Skip to main content

Title: Intermittent Threading Bug — Agent Responses Posted Outside Originating Thread

Feature Request

Severity: Medium-High | Intermittent / Recurring
Agent ID: ff1379fe-51d1-4bd4-a870-e5ef6dc11d88 (Ask_Sam)
Internal Ref: ANT-3200

Bug Description
When Ask_Sam auto-triggers on a new message in #analytics (CCWKC4Z41), responses intermittently post as top-level channel messages instead of thread replies. A secondary related behavior: occasional duplicate responses — two messages fire on the same trigger within seconds.

Expected: All auto-trigger responses post inside the originating thread.
Actual: Response posts at channel level — unanchored, invisible to requestor, clutters channel.

Frequency: Intermittent (~5–10% of triggers). Ongoing for several months. Previously reported; partially resolved; still recurring as of July 6, 2026 (screenshot attached showing ANT-3388 response orphaned at channel level).

Business Impact

  • Requestors miss their answers

  • Channel noise accumulates with context-free orphaned messages

  • Erodes stakeholder trust in agent reliability

  • Directly impacts our internal N6 Operational Reliability KPI (95% target)



Attachment: Screenshot provided showing orphaned response referencing ANT-3388 posted at top-level in #analytics.

Posted by Patrick Codrington ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Dasol Shim

    •

    Jul 29

    Thanks for the detailed write-up — the thread links and timestamps made this easy to pin down.

    We've shipped a fix: replies now stay anchored to the thread the agent was triggered from, instead of relying on prompt instructions. This should also cut down on the duplicate responses. Nothing to change on your end.

    Thanks again for reporting it!☺️