JSM Chat Automations failing due to Slack Events API issue
Incident
Report for Jira Service Management
Resolved
On February 26, 2025 14:45 UTC a temporary Slack outage began which affected JSM automations within Slack.
On February 27, 2025 08:05 UTC we observed new Slack events being processed within JSM successfully. We have confirmed with the Slack team that this outage is resolved.
Slack has advised on their Status page that they do not plan to replay events that were buffered from this incident. For more information on Slack’s update please refer to Slack's status page: https://slack-status.com/2025-02/1b757d1d0f444c34
If you have any further questions please contact our support team.
On February 27, 2025 08:05 UTC we observed new Slack events being processed within JSM successfully. We have confirmed with the Slack team that this outage is resolved.
Slack has advised on their Status page that they do not plan to replay events that were buffered from this incident. For more information on Slack’s update please refer to Slack's status page: https://slack-status.com/2025-02/1b757d1d0f444c34
If you have any further questions please contact our support team.
Update
New Slack events are continuing to get processed within JSM successfully. We are continuing to monitor the situation closely.
We are still awaiting confirmation on when the historical events from the start of the incident will be processed.
For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a
We are still awaiting confirmation on when the historical events from the start of the incident will be processed.
For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Update
New Slack events are continuing to get processed within JSM successfully. We are continuing to monitor the situation closely.
We are still awaiting confirmation on when the historical events from the start of the incident will be processed. For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a
We are still awaiting confirmation on when the historical events from the start of the incident will be processed. For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Monitoring
We have confirmed with Slack that new events are now being processed successfully, and we have validated this within JSM. We continue to monitor the situation closely.
We are still awaiting confirmation on whether historical events from the start of the incident will be processed. For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a
We are still awaiting confirmation on whether historical events from the start of the incident will be processed. For ongoing updates, please refer to Slack's status page: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Update
An issue has occurred where JSM Automations within Slack are not currently triggering actions as expected.
Slack is aware of this issue and is working through their backlog of events.
Atlassian has received a small number of events from this backlog and is monitoring for incoming alerts to be processed.
Slack are providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Slack is aware of this issue and is working through their backlog of events.
Atlassian has received a small number of events from this backlog and is monitoring for incoming alerts to be processed.
Slack are providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Identified
We are aware of an issue where JSM Automations within Slack are not currently triggering actions as expected.
Slack is aware of this issue and is working through their backlog of events that need to be processed.
We are pending Atlassian system events to be processed at this time.
Slack are providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Slack is aware of this issue and is working through their backlog of events that need to be processed.
We are pending Atlassian system events to be processed at this time.
Slack are providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Investigating
We are aware of an issue with JSM Automations within Slack are not currently triggering actions as expected.
We believe that this is related to a current incident that Slack is experiencing with Events API. Slack is providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a
We believe that this is related to a current incident that Slack is experiencing with Events API. Slack is providing updates on this issue on their status page here: https://slack-status.com/2025-02/d41e4bfd1ccae26a
This incident affected: Automation for Jira.