Date Time Trigger Automation Failues

What to do

• Check whether you use Asana in eu. 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 0m it lasted.

  Anything that failed between 2026-04-29 23:19 UTC and 2026-04-21 19:00 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 2

1. resolvedApr 21, 2026, 7:00 PM UTC

   Between April 21st and April 23rd, many rules triggered by date time triggers did not run. New rule triggers ran normally starting April 23rd, and the delayed triggers were processed by April 27th.

   provider

2. postmortemApr 30, 2026, 12:43 AM UTC

   Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour delays in email and inbox notifications in the EU and prevented date time triggers from executing in all regions. Engineers were first alerted on **April 21st** by our monitoring systems, but did not recognize the full scope of the incident until **April 23rd**. On April 23rd, the change to manage date time trigger volume was reverted and the problematic background action jobs were isolated. All delayed notifications were sent by **April 24th, 11:30 AM PDT**, and all delayed date time triggers were executed by **April 27th, 4:00 AM PDT**.

   provider

Corrections

None so far.

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