Jira: Delay in execution of Automation rules
Timeline of updates
- 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.
From Jira’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on jira-software.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Jira, started 2025-10-22 06:20 UTC, resolved after 27 min, 1 update(s).
- Title
- Delay in execution of Automation rules
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/x8vw6z01p2q8
Jira profileRecent Jira incidentsAll outages on October 22, 2025Jira in October 2025MarkdownJSON