botpress node transition missing: conversation stuck

TL;DR

A conversation stuck at a node means the node has no transition matching what the user did: the flow designer covered the expected paths and missed the actual one. Audit every node for a default or catch-all transition, add one where it is missing, and build a stuck-conversation detector that re-engages or escalates stalled sessions. Every node needs an exit for every input, including the unexpected ones.

The query

botpress node transition missing: conversation stuck

Use this when

• Conversations stall with no bot response
• Users report the bot "went silent"
• You are auditing Botpress flows
• Debugging stuck sessions

Not for

• Training Botpress NLU
• Writing node content
• Hosting or scaling Botpress
• Channel configuration

Steps

1. Find the stuck node from session state

Inspect the stalled conversation's current node. The stuck node is the diagnosis: read its outgoing transitions and the user's last input. The gap between the input and the available transitions is the bug.

Expected output: the stuck node and the unmatched input identified.

2. Add a default transition to every node

Every node gets a catch-all transition for unmatched input: clarify, offer options, or escalate. Audit the whole flow for nodes missing one. The default transition is the flow's safety net.

Expected output: no node without a default transition.

3. Route unexpected input to clarification, not silence

The default transition should ask what the user meant or present the valid options, never drop the turn silently. Silence is the worst outcome; a clarifying question keeps the conversation alive.

Expected output: clarifying default transitions everywhere.

4. Detect stuck conversations automatically

Monitor for sessions with no bot response after user input beyond a timeout. Alert or auto-recover: re-engage with a helpful message or escalate to a human. Detection catches the nodes your audit missed.

Expected output: stuck-session detection with recovery.

5. Recover stuck sessions with context intact

When recovering, do not restart the conversation from zero: summarize where it stalled and offer to continue or get help. Losing progress on recovery doubles the frustration.

Expected output: recovery that preserves conversation progress.

Template: the checklist

Stuck node fix:
[ ] Stuck node identified from session state
[ ] Default transition on every node
[ ] Defaults route to clarification, never silence
[ ] Stuck-session detection with auto-recovery
[ ] Recovery preserving conversation context

Variant phrasings

botpress conversation stuck no response

Steps 1 and 2. Find the node, add the default.

bot went silent botpress

Steps 2 and 3. Defaults that clarify.

node has no outgoing transition

Step 2 as the direct fix.

Why it happens

Flow designers think in happy paths: the user picks option A, B, or C, and each gets a transition. Real users type free text, change the subject, or answer a different question. The flow graph covers the designed inputs; reality supplies undesigned ones. Without a default transition, undesigned input has nowhere to go, and the conversation halts.

Edge cases

• Nodes with side effects before the missing transition: if the node already acted (created a ticket), the recovery must account for the partial action.
• Loops back to the same node: a default that returns to the same node without progress creates a loop. Defaults must move forward or escalate.
• Multi-node stalls: sometimes the stall is several nodes deep in a sub-flow. Audit sub-flows with the same rigor.
• Timeouts as transitions: add explicit timeout transitions for nodes awaiting input; do not rely on detection alone.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstEtQZtuAtEkf6WIKMoqsNw