Changes / Jira / Disrupted Automation for Jira triggers not running for some customers
Jira: Major incident: Disrupted Automation for Jira triggers not running for some customers
Summary
A major incident prevented some Automation for Jira rules from executing in Jira and Jira Service Management in Asia Pacific and South East regions; other regions were unaffected. It started 2026-01-06 05:18 UTC and was resolved 2026-01-07 11:32 UTC, lasting 30 h 14 min. New events were fixed, and failed rules were rerun by replaying historical events.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Disrupted Automation for Jira triggers not running for some customers
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-01-06 05:18 UTC
Before: not present
After: 2026-01-07 11:32 UTC
Before: not present
After: Administration, Authentication and User Management, Automation for Jira, Create and edit, Marketplace, Mobile, Notifications, Purchasing & Licensing, Search, Signup, Viewing content
Before: not present
After: We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update within 60 minutes.
Before: not present
After: We have identified the cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information becomes available.
Before: not present
After: Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours.
Before: not present
After: Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted.
Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive.
We have identified the cause and we continue working on restoring the operations back to normal as soon as possible.
In the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule.
We will provide the next update in about two hours or sooner.
Before: not present
After: Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted.
The cause has been identified, and the team is actively working on restoring the operations back to normal as soon as possible.
Workaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule.
We will provide the next update in about two hours or sooner.
Before: not present
After: Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online.
Customers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted.
During Asia Pacific hours tomorrow, the team plans to replay historical events.
Team will continue monitoring. Next update will tomorrow.
Before: not present
After: We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected.
We will provide the next update in about two hours or sooner.
Before: not present
After: We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours.
Based on customer feedback, our team continues monitoring the situation and plans to complete rerunning the remaining Automation for Jira rules that failed earlier.
We will provide the next update once replaying the historical events is complete.
Before: not present
After: Rerunning the remaining Automation for Jira rules that failed for affected customers is complete.
This update resolves the issue.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Disrupted Automation for Jira triggers not running for some customers (this change) A major incident prevented some Automation for Jira rules from executing in Jira and Jira Service Management in Asia Pacific and South East regions; other regions were unaffected. It started 2026-01-06 05:18 UTC and was resolved 2026-01-07 11:32 UTC, lasting 30 h 14 min. New events were fixed, and failed rules were rerun by replaying historical events. | Major incident |