How do you handle silent "False Success" failures in n8n client workflows?
Hey everyone!
Running production n8n workflows for clients, we kept hitting an annoying edge case: a node responds with a 200 OK or green checkmark, but due to API delays, partial payloads, or silent DB rejections, the actual record never gets created.
Curious to hear how other automation builders handle outcome monitoring:
How do you handle silent "False Success" failures in n8n client workflows?
Hey everyone!
Running production n8n workflows for clients, we kept hitting an annoying edge case: a node responds with a 200 OK or green checkmark, but due to API delays, partial payloads, or silent DB rejections, the actual record never gets created.
Curious to hear how other automation builders handle outcome monitoring: