Crons check-in at D+1

[mdefeche]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

We are experiencing random missed check-in notification due to check-in being linked to D+1.

Here is the situation on January 31st. Two crons are logged, one for today (missed) and one for tomorrow (ok).

Expected Result

We expected to have the check in to be linked to the correct date

Actual Result

Check in is linked to the D+1 job

Product Area

Crons

Link

No response

DSN

https://dca869850db34a8a8a4c9fef41bf5840@o1156924.ingest.sentry.io/4503942203310080

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-crons for triage ⏲️

[gaprl]

Hey @mdefeche, we appreciate reporting this issue to us. We can see something is off here -- our team is currently investigated what went wrong, and we'll get back to you on next steps.

[mdefeche]

It looks like raising the grace period to 5min from default helped mitigate the issue