Changes / Drata / Cron service degraded
Drata: Major incident: Cron service degraded
Summary
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 diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Cron service degraded
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-24 18:56 UTC
Before: not present
After: 2026-09-25 16:37 UTC
Before: not present
After: We are currently investigating this issue.
Before: not present
After: We have identified an issue in one of our cron services. We are actively working on a fix.
Before: not present
After: Engineering Team is actively investigating this issue.
Before: not present
After: 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.
Before: not present
After: 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
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: The incident is resolved
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Cron service degraded (this change) 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. | Major incident |