# Jira: Issue with Automation and Connect Apps

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2024-02-28 13:40 UTC · Resolved: 2024-02-28 17:16 UTC · Duration: 3.6 h
- Updates: 1
- [Vendor status page: https://jira-software.status.atlassian.com/incidents/sfb8xzg080jf](https://jira-software.status.atlassian.com/incidents/sfb8xzg080jf)
- [Company: Jira](https://rewindex.com/company/jira.md)

## Timeline of updates

- **resolved** 2024-02-28 17:16 UTC: On 28th Feb between 12:15 UTC and 15:20 UTC Connect apps were unable to perform user-impersonation operations and failed to execute. This had a widespread impact on all product extensions based on the Connect platform resulting in failure when performing actions on behalf of a user. Jira Cloud Automation rules that triggered during the outage may have failed to run. Those rules will not be able to be replayed by customers or Atlassian. Our support engineers have details regarding which customers and automation rules that were impacted. However, support engineers will not be able to replay the failed automation rules. We have identified the root cause of the fault and have resolved it by scaling up the infrastructure. The incident is now resolved. If you have questions or require support - please reach out at https://support.atlassian.com/contact/. We apologise to all of our developers, customers and users who were impacted during this time. We will release a public incident review (PIR) here in the upcoming weeks. We will detail all that we can about what caused the issue, and what we are doing to prevent it from happening again.

_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/sfb8xzg080jf · Markdown: https://rewindex.com/company/jira/incidents/sfb8xzg080jf.md · JSON: https://rewindex.com/api/v1/companies/jira/incidents/sfb8xzg080jf · Generated 2026-10-18T09:42:59.352Z