Changes / Asana / Automation delay
Asana: Major incident: Automation delay
Summary
Asana reported a major incident delaying automations, background actions and webhooks across Australia, EU, Japan and US, from 2025-08-18 01:01 UTC to 2025-08-18 02:43 UTC (1 h 42 min). A conflict between two database management systems caused database locks; core application functions remained available. Asana addressed the root cause and restored normal operations.
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)
Incident page: full timeline of updates →
What changed
Before: not present
After: Automation delay
Before: not present
After: major
Before: not present
After: postmortem
Before: not present
After: 2025-08-18 01:01 UTC
Before: not present
After: 2025-08-18 02:43 UTC
Before: not present
After: Australia - Automations and Background Actions, Automations and Background Actions, EU - Automations and Background Actions, Japan - Automations and Background Actions, US - Automations and Background Actions
Before: not present
After: Asana is currently observing delay for all automations and background actions. Engineers are currently taking steps to mitigate the impact of this delay, and are investigating further to address the root cause.
Before: not present
After: The root cause of automation delay has been addressed, and controls are in place for automations and background actions to catch up on overdue work. Our engineers are monitoring metrics for recovery, and we expect Asana to return to full functionality shortly.
Before: not present
After: Automations and background actions are back to normal operations for all Asana users and customers.
Before: not present
After: **Incident**: Around 2025-08-17 23:35, a conflict occurred between two database management systems. For most Asana customers, database locks prevented execution of background actions, automations, and webhooks were delayed.
**Impact**: Users experienced delays in asynchronous operations, including automations and webhooks. Core application functions remained available and operational throughout the incident. No customer data was lost. The incident lasted approximately 2 hours, after which delayed operations ran normally.
**Moving forward**: Asana engineers completed an investigation into the root cause, and have implemented changes to prevent the conflict between these systems. We are also reviewing our upgrade and management processes to be resilient against similar issues in the future.
Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When | Change | Kind |
|---|---|---|
| Major incident: Automation delay (this change) Asana reported a major incident delaying automations, background actions and webhooks across Australia, EU, Japan and US, from 2025-08-18 01:01 UTC to 2025-08-18 02:43 UTC (1 h 42 min). A conflict between two database management systems caused database locks; core application functions remained available. Asana addressed the root cause and restored normal operations. | Major incident |