Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users

What to do

• Check whether you use Jira Viewing content, Create and edit, Authentication and User Management, Search and 7 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 8h 22m it lasted.

  Anything that failed between 2026-05-13 01:37 UTC and 2026-05-13 09:59 UTC may need a replay.

• Subscribe to Jira's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=jira works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Jira 8

1. investigatingMay 13, 2026, 1:37 AM UTC

   At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

   provider

2. identifiedMay 13, 2026, 2:41 AM UTC

   Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

   provider

3. identifiedMay 13, 2026, 5:38 AM UTC

   The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

   provider

4. identifiedMay 13, 2026, 6:38 AM UTC

   Our team has been able to confirm that new automation events should now be processed correctly. We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

   provider

5. identifiedMay 13, 2026, 7:42 AM UTC

   While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident. We will provide an update on the progress within one hour.

   provider

6. identifiedMay 13, 2026, 8:42 AM UTC

   Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

   provider

7. resolvedMay 13, 2026, 9:59 AM UTC

   We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

   provider

8. postmortemJun 1, 2026, 9:50 PM UTC

   ### Summary ### On May 12, 2026 between 19:01 and 20:46 UTC, a subset of Atlassian customers may have experienced delays in background operations and automation processes. Some background operations, such as notifications or search indexing, were delayed until May 14, 2026 19:25 UTC due to increased cross-region traffic. The issue stemmed from a latent bug in the event processing pipeline. Automated monitoring detected the incident within 16 minutes, and it was mitigated through manual rollback within 1 hour and 45 minutes. Recovery of cross-region event delivery from the affected timeframe took 48 hours due to infrastructure scale constraints. ### IMPACT ### During the incident, customers may have experienced delays in background operations like automation, search indexing, notifications, and permission synchronization. The event processing pipeline distributes events between Atlassian services to support these background operations. - On May 12, 2026, at 19:01 UTC, the deployment of a routing configuration increased event volume across cross-region services. At 20:46 UTC, rolling back routing configurations resolved the issue. - Processing the accumulated cross-region message backlog finished by May 14, 2026, at 19:25 UTC. **Automation & Jira Service Management** Some Atlassian customers experienced event-triggered rules delayed or executed multiple times during the recovery window. **Confluence** Some Atlassian customers experienced delays in search indexing and possible duplicate notifications and automation rule executions during the recovery window. ### ROOT CAUSE ### The issue arose from the deployment of a routing configuration change to the event processing platform, exposing a latent bug in legacy configurations. This change distributed higher volume of events to cross-region services. Cross-region services validated and discarded extra events but needed greater scale to handle the increased influx. The mitigation involved rolling back the configuration change in the event platform. Recovery involved scaling cross-region services to handle higher inbound traffic. ### REMEDIAL ACTIONS PLAN & NEXT STEPS ### We know that performance degradations impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified because the change was related to a very specific kind of legacy case that was not picked up by our automated continuous deployment suites and manual test scripts. We are prioritizing the following improvements to help prevent similar incidents in future: - Enhance runtime metrics across critical-path configurations to predict change impact before deployment. - Enhance failover capabilities to create and replace infrastructure components to respond faster to increased processing demands. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.