Hi Everyone!
I’m encountering a recurring issue with a workflow that utilizes a WhatsApp trigger and a Postgres chat memory node.
While the initial processing of messages from the WhatsApp bot works correctly and results in a successful workflow execution, I consistently receive three subsequent workflow errors immediately after each success.
The error message points to the ‘Postgres Chat Memory1’ sub-node:
Error in sub-node ‘Postgres Chat Memory1’
Investigating the data associated with these errors suggests they are triggered by incoming WhatsApp message status updates. The schema of this status update data appears to differ from the schema used for the initial successful message data, which seems to be causing the failure in the Postgres memory node.
A key constraint is that I cannot change the key or modify how the Postgres memory node handles the incoming data schema.
Has anyone experienced a similar problem or have any ideas on how to resolve this schema mismatch or prevent the memory node from processing the status update data?
Thanks in advance!