Thanks for sharing your findings Marc.
I had a look through the Bot Flow actions as well and couldn't find an obvious way to introduce a short delay or pause without relying on an Ask action. Unfortunately, I wasn't able to find a Bot Flow equivalent to a Wait/Sleep action either.
Interested to see if anyone has implemented a different approach for this type of asynchronous polling scenario.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 06-16-2026 05:36
From: Marc GEWINNER
Subject: Similar to "Flush Audio" in a Bot Flow.
Hello
Test done the Set Language doesn't "flush" the audio.
The only action I can use is an Ask ... waiting a user input flushes the audio (yes tricky ! ). In my case I tested a Ask Yes/No with the ^rompt I want to play as question.
But I have the No Input Timeout being set for the whole bot flow, in my case 8 seconds that is too long and my loop takes more time than what I want.
Regards
Marc
------------------------------
Marc GEWINNER
other
------------------------------
Original Message:
Sent: 06-16-2026 03:19
From: Marc GEWINNER
Subject: Similar to "Flush Audio" in a Bot Flow.
Thanks for your answer Harisankar
I'm not passing data from a Inbound call flow to a Bot flow but from a Workflow to a Bot flow. The only way I know in Architect to get data from a Workflow is to use participant data.
And in my case the data action request takes between 3 and 10 seconds to answer, in more than 99% of the cases Participant Data are set quicker than this.
Regards
Marc
Marc
------------------------------
Marc GEWINNER
other
------------------------------
Original Message:
Sent: 06-16-2026 00:53
From: Harisankar Thangavelu
Subject: Similar to "Flush Audio" in a Bot Flow.
If you are passing data from an inbound call flow into a bot flow, the recommended approach is to use bot input variables rather than relying on participant data.
Participant data updates can have a delay, and the bot flow may attempt to read the values before they are available, even if they were set correctly in the inbound flow before transferring to the bot.
If you still want to use a retry/loop approach, you can use a Communicate block with blank audio (for example, 5 seconds) between attempts. Keep the retries limited (maximum 3 loops) to avoid creating an unintended infinite execution path.
------------------------------
Harisankar Thangavelu
Senior Application Engineer
------------------------------