In a Slack thread, Junior's first public response addressed an earlier bot notification rather than the direct @junior mention that actually triggered the run. The real work was then completed silently in a second response with no acknowledgment of the original instruction.
Observed sequence (thread: https://sentry.slack.com/archives/C0BF6P51F9B/?thread_ts=1783543410.014679):
1783543450 — Linear bot posts a notification in the thread1783543646 — User directly mentions @junior with an instruction to create draft PRs1783543897 — Junior replies: "just the linear bot linking the ticket — nothing to act on here." (addresses the bot notification, not the mention)1783544038 — Junior replies: "plan looks clean — 8 resources to add…" (ran a terraform plan silently, no acknowledgment of instruction)- PR
getsentry/datadog-terraform#576 was created, but the user had to explicitly ask "uh, is there a PR?" before Junior surfaced the link
Expected: The run triggered by a direct @junior mention anchors on that mention message and acknowledges the task. Intermediate bot messages in the thread do not receive their own response.
Actual: First response addressed the bot notification. Real work ran in a separate response with no connection to the instruction.
Hypotheses (unconfirmed — logs needed to distinguish):
- Possible duplicate run / double-enqueue via
completeConversationWork treating awaiting_resume as runnable (known bug)
- Possible current-message selection bug where the turn's anchored message pointed at the bot notification instead of the mention
- Possible bot/thread-event filtering regression treating intermediate bot messages as actionable
- Possible message-handling behavioral change that was not yet complete at the time
Debugging signals to collect:
- Run/conversation IDs for Junior messages at
1783543897 and 1783544038
- Triggering Slack event and
current_message_ts for each run
- Whether both posts originated from the same conversation turn or separate turns
- Queue state transitions and
completeConversationWork status around those timestamps
--
View Junior Session in Sentry
In a Slack thread, Junior's first public response addressed an earlier bot notification rather than the direct
@juniormention that actually triggered the run. The real work was then completed silently in a second response with no acknowledgment of the original instruction.Observed sequence (thread: https://sentry.slack.com/archives/C0BF6P51F9B/?thread_ts=1783543410.014679):
1783543450— Linear bot posts a notification in the thread1783543646— User directly mentions@juniorwith an instruction to create draft PRs1783543897— Junior replies: "just the linear bot linking the ticket — nothing to act on here." (addresses the bot notification, not the mention)1783544038— Junior replies: "plan looks clean — 8 resources to add…" (ran a terraform plan silently, no acknowledgment of instruction)getsentry/datadog-terraform#576was created, but the user had to explicitly ask "uh, is there a PR?" before Junior surfaced the linkExpected: The run triggered by a direct
@juniormention anchors on that mention message and acknowledges the task. Intermediate bot messages in the thread do not receive their own response.Actual: First response addressed the bot notification. Real work ran in a separate response with no connection to the instruction.
Hypotheses (unconfirmed — logs needed to distinguish):
completeConversationWorktreatingawaiting_resumeas runnable (known bug)Debugging signals to collect:
1783543897and1783544038current_message_tsfor each runcompleteConversationWorkstatus around those timestamps--
View Junior Session in Sentry