Confluence: Delay in execution of Automation rules
Affected components: Confluence Automations
Timeline of updates
- investigating
We understand that our customers are experiencing delay in execution of Automation rules. While our team is investigating further on this, it looks like a follow-on effect of the recent AWS outage.
We continue to investigate further on this and we shall keep you informed of the progress every hour if not sooner. - identified
Atlassian team has identified the cause of the issue that led to delay in execution of Automation rules. This is a follow-on effect of the recent AWS outage.
We shall keep you informed of the progress every hour, if not sooner. - resolved
Our teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage.
This issue is marked as resolved.
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
92e893c10ab403b3…
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: minor) posted by Confluence, started 2025-10-22 06:20 UTC, resolved after 27 min, 3 update(s).
- Title
- Delay in execution of Automation rules
- Vendor
- Confluence
- Date
- URL
- https://rewindex.com/company/confluence/incidents/wn25kdl448xp
Confluence profileRecent Confluence incidentsAll outages on October 22, 2025Confluence in October 2025MarkdownJSON