Service Slowness in Multiple Products

Between 09:43 UTC to 15:55 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 15:55 UTC, we anticipate processing to be completed by 08:00 UTC March 18th, 2025. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay.

For automation processes initiated before 15:55 UTC on March 17th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

Following our previous update, we continue to experience delays in automation processing across Jira, Jira Service Management, and Confluence. The issue persists, affecting all automation customers and causing rules to appear stuck. Our team is actively working to resolve the situation and restore normal service levels as quickly as possible. We appreciate your patience and will provide further updates as more information becomes available.

We are currently experiencing delays in automation processing across Jira, Jira Service Management, and Confluence due to high traffic. While rules are firing, execution is delayed. Rules triggered in the last 2.5 hours will be processed, but this may take up to a day. New events should process normally following adjustments made at 12:13 PM UTC to prioritize them. We will provide an update in the next hour. Thank you for your patience.