Skip to content
Asana · Apps and SaaSAug 18, 2025, 01:01 UTC

Automation delay

MajorNot disclosedUpdated 18h ago
Aug 18, 01:01 UTCAug 18, 02:43 UTC
Duration
1h 42m
Impact
Major
Root cause
Not disclosed
Asana, 90 days
6 incidents
Affected
Automations and Background ActionsUS - Automations and Background ActionsEU - Automations and Background ActionsJapan - Automations and Background ActionsAustralia - Automations and Background Actions
Status page

Final update

**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.

Timeline

  1. Postmortem · Aug 20, 00:02 UTC
    **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.
  2. Resolved · Aug 18, 02:43 UTC
    Automations and background actions are back to normal operations for all Asana users and customers.
  3. Monitoring · Aug 18, 01:41 UTC
    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.
  4. Identified · Aug 18, 01:01 UTC
    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.

More from Asana

Full history

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.