Summary
When a tool-backed query runs for an extended period (~5 minutes) and then stops or times out, the assistant produces no visible response — not even an error or explanation. The user is left with no indication of what happened or what to do next.
Reproduction
- Trigger a request that requires live data lookup (e.g. querying Sentry telemetry for a specific service).
- The assistant begins tool work but the operation exceeds the execution window.
- No reply is posted to the thread.
Expected behavior
The assistant should always post a final response, even on timeout or failure. At minimum, a message explaining that the operation did not complete and offering next steps (e.g. retry, manual link, or fallback answer).
Versions affected
Observed in production. Version context from runtime metadata at time of report: c8343126c7d1fb9a736d7cc1e331965fc6bb8988.
Action taken on behalf of Michael Warkentin.
Summary
When a tool-backed query runs for an extended period (~5 minutes) and then stops or times out, the assistant produces no visible response — not even an error or explanation. The user is left with no indication of what happened or what to do next.
Reproduction
Expected behavior
The assistant should always post a final response, even on timeout or failure. At minimum, a message explaining that the operation did not complete and offering next steps (e.g. retry, manual link, or fallback answer).
Versions affected
Observed in production. Version context from runtime metadata at time of report:
c8343126c7d1fb9a736d7cc1e331965fc6bb8988.Action taken on behalf of Michael Warkentin.