Drata: Some Automatic Compliance tests are delayed
Drata reported a major incident globally delaying some Automatic Compliance test results, leaving workflows in “testing” longer than expected. It ran from 2026-04-23 16:34 UTC to 2026-04-23 18:42 UTC (2 h 8 min). A fix was deployed and the queue returned to normal; Drata anticipated no data loss because workflows were safely queued.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: API USUS - API US
Timeline of updates
- investigating
Our team is currently investigating an issue causing some Automatic Compliance test results to be globally delayed. During this time, you may see workflows remain in the “testing” state longer than expected while we work on a fix. At this point, we do not anticipate any data loss, as workflows are being safely queued in our backend system.
- monitoring
A fix for the issue with Automatic Compliance tests results has been deployed. The queue is re-processing. We are actively monitoring the remediation status.
- resolved
The incident has been resolved. The queue is back to normal and processing all tasks on time.
Rewindex changes for this incident
- Major incident: Some Automatic Compliance tests are delayed 2026-04-23 16:34 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