Asana: Automation delay
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 archived incident (Sol). Check the timeline before relying on it.
Affected components: Automations and Background ActionsEU - Automations and Background ActionsAutomations and Background ActionsJapan - Automations and Background ActionsAutomations and Background ActionsUS - Automations and Background ActionsAustralia - Automations and Background ActionsAutomations and Background Actions
Timeline of updates
- identified
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.
- monitoring
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.
- resolved
Automations and background actions are back to normal operations for all Asana users and customers.
- postmortem
**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.
Rewindex changes for this incident
- Major incident: Automation delay 2025-08-18 01:01 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Asana profile · Recent Asana incidents · Markdown · JSON