Respond.io incident

Workflow “Close Conversation” Step Fails to Close Conversations

Minor Resolved View vendor source →

Respond.io experienced a minor incident on August 19, 2026 affecting Workflows (Workflows), lasting 1h 30m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2026, 06:30 AM UTC
Resolved
Aug 19, 2026, 08:00 AM UTC
Duration
1h 30m
Detected by Pingoru
Aug 19, 2026, 06:30 AM UTC

Affected components

Workflows (Workflows)

Update timeline

  1. identified Aug 19, 2026, 06:30 AM UTC

    We are currently experiencing an issue where the “Close Conversation” step in Workflows is not closing conversations as expected. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the inconvenience and will provide an...

  2. investigating Aug 19, 2026, 07:20 AM UTC

    Our engineering team has identified the root cause of the issue affecting the “Close Conversation” step in Workflows and AI Agent conversations . A mitigation has been applied, and conversations can now be closed as expected. Our engineering team is currently working on...

  3. resolved Aug 19, 2026, 08:00 AM UTC

    We are happy to report that the issue affecting the “Close Conversation” step in Workflows has been resolved. Our engineering team has fully deployed the fix and verified that conversations are now closing as expected. We will continue to monitor the platform to ensure...