← Back to Jira History
major✓ Resolved
Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users
Status
resolved
Duration
8h 22m
Updates
6
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedWed, May 13, 2026, 10:00 AM
This incident has been resolved.
identifiedWed, May 13, 2026, 08:42 AM
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.
identifiedWed, May 13, 2026, 07:42 AM
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.
identifiedWed, May 13, 2026, 06:38 AM
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.
identifiedWed, May 13, 2026, 05:38 AM
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.
identifiedWed, May 13, 2026, 02:41 AM
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.
investigatingWed, May 13, 2026, 01:37 AM
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.
📊 TECHNICAL DETAILS
Internal ID
be1e6fb8-2f82-4178-8a04-aca58b9e9558
External ID
90cyzwh234yl
🕐 Started
Wed, May 13, 2026, 01:37 AM
🔄 Last Updated
Wed, May 13, 2026, 10:00 AM
✓ Resolved
Wed, May 13, 2026, 10:00 AM
MAJOR
Impact Level
8h 22m
Total Duration
6
Status Updates
Affected Components
Automation for Jira
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed