Sense incident

Chatbot Errors

Critical Resolved View vendor source →

Sense experienced a critical incident on May 28, 2026 affecting Sense Chatbot, lasting 2h 14m. The incident has been resolved; the full update timeline is below.

Started
May 28, 2026, 07:16 PM UTC
Resolved
May 28, 2026, 09:30 PM UTC
Duration
2h 14m
Detected by Pingoru
May 28, 2026, 07:16 PM UTC

Affected components

Sense Chatbot

Update timeline

  1. investigating May 28, 2026, 07:16 PM UTC

    We are seeing reports of users unable to build or access chatbot conversations due to a 500 error. Our team is actively investigating this issue and we'll provide updates as they are received.

  2. monitoring May 28, 2026, 08:30 PM UTC

    Our team has identified the issue causing errors and latency in Sense Chatbots and has deployed a fix. Any Chatbots missed during this downtime will need to be re-triggered to ensure all answers are logged as expected. We will monitor to ensure we don't see these issues recur. If you believe you are still facing issues, please submit a support ticket at https://support.sensehq.co/hc/en-us/requests/new and our team will review.

  3. resolved May 28, 2026, 09:30 PM UTC

    After monitoring, we are seeing stability in the Chatbot product once more, and no longer seeing any errors populate. Any Chatbots missed during this downtime will need to be re-triggered to ensure all answers are logged as expected. Our team will be reaching out by customer for bots affected during this time. We will monitor to ensure we don't see these issues recur. If you believe you are still facing issues, please submit a support ticket at https://support.sensehq.co/hc/en-us/requests/new and our team will review.