# Jira: Automations and rules issue

- Impact (vendor’s label): major
- Status: resolved
- Started: 2023-06-13 19:59 UTC · Resolved: 2023-06-14 03:02 UTC · Duration: 7.0 h
- Updates: 1
- [Vendor status page: https://jira-software.status.atlassian.com/incidents/g84s6dz9frd0](https://jira-software.status.atlassian.com/incidents/g84s6dz9frd0)
- [Company: Jira](https://rewindex.com/company/jira.md)

## Timeline of updates

- **resolved** 2023-06-14 03:02 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/jira/incidents/g84s6dz9frd0 · Markdown: https://rewindex.com/company/jira/incidents/g84s6dz9frd0.md · JSON: https://rewindex.com/api/v1/companies/jira/incidents/g84s6dz9frd0 · Generated 2026-10-18T11:44:27.613Z