It would be nice to add the ability to enable a Timeout for a specific capture input card. This would be a way to handle the following scenarios: 1. Users often respond to questions in multiple input messages. This could be happen for a variety of reasons including but not limited to: - The user accidentally hit send before completing their answer - The user wants to add on to what they sent earlier - The user made a mistake and wants to correct what they just sent When this happens, it can break the chatbot flow since the bot processes the first input and the flow progresses causing a bad user experience. Having a timeout on individual capture cards would allow us to wait for a bit to allow the user to stop typing, aggregate all the user messages and then process the entire user input in one shot in the context where it makes sense. 2. This would also be useful for a learning assistant bot similar to the one @acceptable-gold-88171 built during his office hours that quizzes the user. You can give the user a limited amount of time to answer before moving on to the next question. 3. If the user enter the timeout workflow, we could ask them if they are still there and want to continue the conversation with a shorter timeout and if they don't respond within the shorter timeout, we could end the conversation. This would also require a [feature](https://discord.com/channels/1108396290624213082/1157812772843823155) to allow the user to return to the part of the flow the bot was in when the timeout was triggered.

This is really well explained. Thanks for that @cool-summer-17043

This would be great to keep the conversation moving instead of directly going to the timeout flow, this could allow the bot to send out a message asking if the user is not sleeping and if he still does not respond send to the next card where all the data in variables like name, conversation summary... could be sent out to API , then go to timeout flow and shut down the bot. This will also solve the issue we have been speaking with @famous-jewelry-85388 about sending out variable values from the timeout flow, because we have no problems sending out from any workflow, this is the thread: https://discord.com/channels/1108396290624213082/1151247805365629032 Also another thread would be solved with card timeout: How to know when someone quit @full-gpu-42216 https://discord.com/channels/1108396290624213082/1160576292979216464

@acceptable-smartphone-22753 👍