Drata: Cron service degraded
Drata reported major cron service degradation affecting background tasks that flag expired reports, update approval statuses, apply policies, and recalculate control readiness, potentially leaving compliance data stale. It started at 2026-09-24 18:56 UTC and was resolved at 2026-09-25 16:37 UTC, lasting 21 h 40 min; a fix was deployed and monitored.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Timeline of updates
- investigating
We are currently investigating this issue.
- investigating
We have identified an issue in one of our cron services. We are actively working on a fix.
- investigating
Engineering Team is actively investigating this issue.
- investigating
We have identified the root cause of the cron service degradation and are working to deploy fix. The cron service that was impacted automatically runs background tasks that keep compliance data fresh. It flags expired reports, updates approval statuses when deadlines hit, applies new policies, and recalculates control readiness.
- investigating
Fix has been deployed. We will be monitoring the next cron run to ensure incident has been fully resolved. The next cron run is scheduled for 11:00 UTC
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
The incident is resolved
Rewindex changes for this incident
- Major incident: Cron service degraded 2026-09-24 18:56 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Drata profile · Recent Drata incidents · Markdown · JSON