Crons ingestion backlogged
Jan 23, 18:38 UTCJan 24, 00:27 UTC
Duration
5h 49m
Impact
Informational
Root cause
Not disclosed
Sentry, 90 days
25 incidents
Affected
Not listed by the vendor.
Final update
Backlog has been processed and crons should be running as normal
Timeline
- Resolved · Jan 24, 00:27 UTC
Backlog has been processed and crons should be running as normal