Jira: Automation rule execution are delayed
Timeline of updates
- resolved
Between 13:00 UTC to 16:30 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay. For automation processes initiated before 16:30 UTC, they may take until 08:00 UTC March 19th, 2025, however, we anticipate processing to be completed quicker. No action is required from users for these automations to be completed.
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-03-18 15:04 UTC, resolved after 2.4 h, 1 update(s).
- Title
- Automation rule execution are delayed
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/7zr6j37r9zbp
Jira profileRecent Jira incidentsAll outages on March 18, 2025Jira in March 2025MarkdownJSON