Changes / Drata / Some Automatic Compliance tests are delayed
Drata: Major incident: Some Automatic Compliance tests are delayed
Summary
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 diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Some Automatic Compliance tests are delayed
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-23 16:34 UTC
Before: not present
After: 2026-04-23 18:42 UTC
Before: not present
After: API US, US - API US
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: The incident has been resolved. The queue is back to normal and processing all tasks on time.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Some Automatic Compliance tests are delayed (this change) 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. | Major incident |