Jira: Automations and rules issue
Timeline of updates
- resolved
Between 6:49PM UTC to 8:45PM UTC, AWS API Gateway and AWS Lambda were down. During this time, events from Jira products and Confluence were not received by Automation. These events will not trigger the automation. The AWS services have recovered from an outage at 8:45PM UTC. Automation events for Confluence during that time have been reprocessed, however, events for Jira were not received and can't be recovered. After the AWS services came back online, Automation started processing any events triggered after 8:45PM UTC. Due to the volume, this caused some events to become backlogged, however, these have now been processed successfully. All new executions after the recovery are confirmed operating normally. For any further issues, kindly reach out to Atlassian support.
From Jira’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on jira-software.status.atlassian.com (opens in new tab). Jira profile · Recent Jira incidents · Markdown · JSON