Asana: Date Time Trigger Automation Failues
Timeline of updates
- resolved
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.
- postmortem
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ef65e60a03625ad2…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Asana, started 2026-04-29 23:19 UTC, resolved after -11780 min, 2 update(s).
- Title
- Date Time Trigger Automation Failues
- Vendor
- Asana
- Date
- URL
- https://rewindex.com/company/asana/incidents/1gqq6vz0195q
Asana profileRecent Asana incidentsAll outages on April 29, 2026Asana in April 2026MarkdownJSON