Currently, when there is a failure in the webhook via chatbot (whether in the webhook node or in the OpenAI node), if we want to handle this failure, we need to create a structure that may involve a “New choice” node (to check if there is a webhook failure), a variable (optional, if we want to count the number of failures differently for each one), “Wait for response” (for X amount of time), “Sleep,” and “Jump to” nodes to go back to the Webhook or OpenAI node.
When there is a webhook failure, it’s not possible to use a “Jump to” back to the webhook or OpenAI node to avoid an infinite loop, making it mandatory to have a “Wait for response” node in between. But it also wouldn’t be viable to wait for a response without a timeout, because if the contact doesn’t interact, we would never be able to make a new request. And if the person replies and we don’t use a “Sleep” node before the “Jump to,” that branch merges (I admit I’m not entirely sure if this works or not, but I believe it might be a bug — sample video attached).
It would be practical to handle these failures directly in the Webhook or OpenAI nodes with a “Retry on fail” action, with a “Maximum attempts” and “Wait between attempts (ms).”


Please authenticate to join the conversation.
Open
Feature Request
10 months ago

Bryan
Get notified by email when there are changes.
Open
Feature Request
10 months ago

Bryan
Get notified by email when there are changes.