Heeeeeelp
Objet : Problème avec le déclenchement du No Reply
Hello Voiceflow team,
I’m facing an issue with the No Reply function in my flow.
Here’s what I did step by step:
I set Inactivity time = 2 seconds.
I set Reprompts = 0.
I turned Follow path after reprompts = ON.
I connected the No Reply port directly to the next block.
I tested both in the editor (Run/Test) and on my published bot.
Expected behavior:
After 2 seconds of silence (no button click, no input), the flow should automatically continue to the next block.
Actual behavior:
The assistant stays stuck at the Button step.
I can see the timer counting, but the No Reply port never fires.
I also made sure:
My prompt is shorter than 2 seconds (so the TTS length is not the problem).
I cleared the session, tested in incognito, and started a fresh conversation.
I checked that there are no Commands intercepting the input.
Still, the No Reply does not trigger as expected in test mode.
Could you please check if this is a bug or if there’s something else I should configure differently?
Thanks a lot for your help 🙏
2 Replies
Here’s what’s happening 👇
The No-Reply path is only evaluated after the step has completed at least one “reprompt” cycle. When the counter is set to
– When the counter is 0 there is nothing to “exhaust”, so the path is never evaluated. Extra notes • In production chat UIs you’ll still need a small client-side timer that, after the
0 reprompts, the runtime stays in a permanent “listening” state and the No-Reply port is never considered – that’s why you see the timer but nothing fires.
Fix
1. Edit the Button step and keep No-Reply ON.
2. Add 1 reprompt (you can leave the message blank or write something short like “…”).
3. Leave “Follow path after reprompts” ON.
4. Keep your 2-second inactivity timeout.
Flow → after 2 s with no input the bot will fire the reprompt once; immediately after that single reprompt the No-Reply port will be triggered and the conversation will move to the next block.
Why it works this way
– The logic described in the docs (“after the set number of reprompts are exhausted, the conversation will follow the No-Reply path”) expects the counter to be ≥ 1.– When the counter is 0 there is nothing to “exhaust”, so the path is never evaluated. Extra notes • In production chat UIs you’ll still need a small client-side timer that, after the
timeout seconds, sends a type: "no-reply" request to the Dialogue Manager if you want the same behaviour outside of Voiceflow’s Test tool (see docs: No-Reply handling → “Handling No Reply in production”).
• Minimum practical timeout is usually 3-5 s; some browsers can throttle shorter setTimeouts when the tab isn’t focused.
Give the reprompt-count tweak a try and the No-Reply path should fire as expected ✅despite the noanswer activated with 1 short reprompt and the following path after reprompt it still does not work
Subject: No Reply not triggering consistently in Capture and Button blocks
Hi Voiceflow team,
I’m having trouble getting the No Reply behavior to work consistently:
1. With a Capture block:
• I enabled No Reply, set inactivity to 5s, added a short reprompt, and wired the No Reply port.
• In test mode, sometimes the reprompt shows once but the No Reply path never executes.
• Most of the time, neither the reprompt nor the No Reply triggers.
2. With a Button (Listen) block:
• In the Voiceflow Studio test environment, No Reply works correctly (reprompt + No Reply port firing).
• But once I publish the project and embed the widget on another site, the No Reply never fires.
• The only way to make it work again is to refresh the chatbot and start a New Chat.
Expected behavior:
After 5 seconds of inactivity, the reprompt should appear (if configured), and after that the flow should follow the No Reply port automatically.
Actual behavior:
• Capture block → No Reply almost never works.
• Button block → works in Studio Test, but does not work once published on a site unless I manually reset the chat.
Could you clarify:
• Why the Capture block No Reply doesn’t trigger at all?
• Why the Button block No Reply works in Studio but not in a published webchat without refreshing?
• What is the correct way to handle No Reply in a published chatbot (do we need to send a no-reply event manually from the frontend)?
Thanks a lot for your help 🙏