Automation delay

What to do

• Check whether you use Asana Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 42m it lasted.

  Anything that failed between 2025-08-18 01:01 UTC and 2025-08-18 02:43 UTC may need a replay.

• Subscribe to Asana's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=asana works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Asana 4

1. identifiedAug 18, 2025, 1:01 AM 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.

   provider

2. monitoringAug 18, 2025, 1:41 AM 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.

   provider

3. resolvedAug 18, 2025, 2:43 AM UTC

   Automations and background actions are back to normal operations for all Asana users and customers.

   provider

4. postmortemAug 20, 2025, 12:02 AM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.