Intermittent failures due to Slack outage

This incident is confirmed resolved.

Risotto Slackbot continues to operate as expected, despite the continuing Slack incident (https://slack-status.com/2025-02/d41e4bfd1ccae26a). We will resolve this incident once Slack has given the clear.

Slack has reported that the incident with messaging has been resolved (https://slack-status.com/2025-02/d41e4bfd1ccae26a) and we began to see some recovery of Slackbot functionality around 2 AM Pacific, however we are monitoring and will resolve the alert when Slack resolves the incident completely.

Slack has reported a separate issue (https://slack-status.com/2025-02/d41e4bfd1ccae26a) that continues to impact Risotto Slackbot functionality. They are reprocessing a backlog of messages, so Risotto may respond late or sporadically. We will continue to monitor the incident and will update this once service is fully restored.

Slack has resolved the issue, but we are still getting reports of the Risotto chatbot not functioning correctly. We are investigating.

Slack is still working to restore service (https://slack-status.com/2025-02/1b757d1d0f444c34).

Slack is still working to restore service (https://slack-status.com/2025-02/1b757d1d0f444c34).

We are seeing some recovery taking place, though Slack is still working to restore service (https://slack-status.com/2025-02/1b757d1d0f444c34)

We are seeing an elevated error rate due to a Slack incident (https://slack-status.com/2025-02/1b757d1d0f444c34). This is resulting in sporadic unresponsiveness from Risotto's Slackbot, as well as repeated messages.

We are monitoring and will post updates to this page.