Unable to perform UI Operations
Incident
Report for Jira Work Management
Resolved
Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira.
Impact
Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes.
Current Status
The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume.
Next Steps
We are conducting a root cause analysis of the internal service. A post incident review will be conducted.
Impact
Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes.
Current Status
The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume.
Next Steps
We are conducting a root cause analysis of the internal service. A post incident review will be conducted.
Monitoring
We have recovered from a issue which saw degraded Automation experience.
Impact
Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running.
Current Status
The incident has been mitigated and we continue to investigate the cause of this incident
Next Steps
We are continuing to monitor the service, and will provide further updates in the next two hours
Impact
Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running.
Current Status
The incident has been mitigated and we continue to investigate the cause of this incident
Next Steps
We are continuing to monitor the service, and will provide further updates in the next two hours
Update
Atlassian team is actively investigating the issue with UI based Customer interactions.
Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures.
We shall keep you informed of the progress in next 2 hours, if not sooner.
Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures.
We shall keep you informed of the progress in next 2 hours, if not sooner.
Investigating
UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.
This incident affected: Automation for Jira.