Error handling issue after updating to version 1.85.4 – workflows return 200 even on failure

Hi everyone,

After updating to version 1.85.4, I noticed an unexpected change in how errors are handled in my workflows. Previously, when a workflow failed (e.g., due to an unhandled exception in a node), it returned an HTTP 500 along with the classic "Workflow error" message.

Now, however, all workflows that fail are returning HTTP 200, even though they clearly encountered an error. This is causing issues for me because my external services can no longer properly detect when a workflow has failed, and I need to implement workarounds to catch errors manually.

I’m currently testing the flows using Postman, and even when there’s a clear failure, the response is still 200. I haven’t modified any workflow logic or error-handling code — the only change was the version upgrade.

Is this behavior intentional in this version? Or is there a setting I might be missing to restore the previous error-handling behavior?

Thanks in advance.

Matias

Hi everyone!
I’ve decided to close this post since I found a workaround that works well for my case.
Basically, I implemented a callback system on my backend: when the flow succeeds, it calls a success callback, and when it fails, I trigger a generic error handler that posts to a separate error callback endpoint. That way, I can control everything from my side.

Thanks to everyone who checked in!
—Matias

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.