Repository navigation
Send a Chat message again when the bridge never got its prompt - #788
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
czpython
force-pushed
the
chat-delivered-after-prompt
branch
from
October 3, 2026 10:25
bfc6603 to
dc807f9
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
send_turnmarks a message delivered before it sends the prompt. When the prompt request failed, the next delivery asked the bridge for its status, saw another message ID, and marked the turn interrupted. The message was never sent.The bridge records the message ID when it accepts a prompt, so that ID tells the two failures apart. When the bridge holds the message, the prompt arrived and Druks follows the turn, as before. When the bridge is idle, replied, or cancelled with another ID, the prompt never arrived:
follow_turnnow puts the turn's messages back to pending, and the delivery loop sends them again. The bridge refuses a prompt for an ID it already accepted, so a turn never runs twice. A missing or interrupted bridge still ends the turn as interrupted.docs/chat.mddescribed delivery as at most once with no automatic re-send. It now describes the bridge's ID as the point that decides.Fixes #785
🤖 Generated with Claude Code