Whats App Business Cloud / Open AI chat bot error

[Steve-fox]

Hi gang, can anyone help with this scenario, I’m trying to run a chat bot over WhatsApp and have pretty much nailed it. I have filters set up that work out whether a conversation already exists and if it does then the thread id is passed to that module and the assistant responds accordingly. The issue I have is when I connect up the final send message module and Open Ai module on the ‘Chat doesn’t exist’ path throws this error.

BundleValidationError

Validation failed for 1 parameter(s).

• Missing value of required parameter ‘message’.

If I add a module that adds a spreadsheet row rather than sends a Whats App message then the scenario works fine. It’s only errors after a message is sent at the end as it seems to run the scenario again. It immediately sees the response as a new message and then forces it down the chat doesn’t exist route. If I then run the scenario again and reply to the chat bot on Whats App the filters works and it goes down the ‘chat exists’ route and resposnds okay, but it will still throw the error afterwards. I cannot for the life of me figure it out.

SWIFT_Bot_blueprint.json (124.2 KB)

[duativ]

@Steve-fox try to set your “chat doesn’t exist” filter as a fallback route like this:

By default (no routes set as fallback route) both routes will be attempted,
If second route is set as fallback, it will only be attempted if first route filter wasn’t passed

I’m not sure if this will solve your issue, what you could also do is adding a second condition to second route filter that checks if {{9.messages.text.body}} exists

[duativ]

another thing you could look into is if you can filter the type of events that you are watching

[Steve-fox]

I’ve solved this or rather I hired someone to solve it. The issue stemmed from the Whats App business cloud Watch Event module, it was triggering the scenario again when the message was read (it turns out it watches all events not just new messages ) so when it run again there was nothing in the message variable. A filter had to be added just after the module which stopped empty message variables getting through.