When I use this workflow, to respond to chat queries, in test mode everything runs fine.
However as soon as I try and run it in production mode 3 requests come through with the first one being successful and the next 2 presenting as errors leading to an error response on the chatbox page. These errors of course make the automation unusable.
I am wondering how to stop multiple requests from coming through the workflow to stop the 2 errors.
What is the error message (if any)?
The error message says “Invalid ‘thread_id’: ‘null’. Expected an ID that begins with ‘thread’.” because the first one is going down the false path but the other 2 down the true so it cant set a thread_ID as it isn’t created at that point.
There is no difference with the request. I can put 1 request into the chatbox in test mode and it will run fine but put the same request when in production mode once and it will run 3 times for some reason and succeed the first and fails the other 2 and so doesnt output a response
then is it possible if you show us? because this is a thing with webhook in production and in test mode
where in test mode, you only listen(activate) to it when u want to, while when it’s on production mode, it listens everything
for example, a whatsapp webhook, for 1 message, it can trigger the webhook 4 times, because it will trigger for every event happening in the message (message sent, delivered, read, deleted) etc.
so im guessing tht most likely its also the same case with u
so if u can kindly go to the execution tab and maybe share with us the failed execution data and the success one on the webhook trigger node, then maybe we can help u better
