Why does the Firestore node send error details to the success branch using the 'Continue (using error output)' option?

When you enable the “Continue (using error output)” option on a node (in this case the Firestore node), the intent is to have the node handle errors gracefully without halting the workflow. In practice, this means that even if an error occurs, the node will still produce output on the “success” branch. However, the output will contain details about the error that occurred.

In other words, the Firestore node isn’t “throwing” an exception that routes the data to the dedicated error branch; instead, it’s attaching error information to the regular output. This behavior is expected when you use that option. If you want the workflow to branch off to a separate error path when an error happens, you’d need to disable that option so that the node stops on error.

If your processing logic further down the workflow needs to handle the error details, you can check the structure of the node’s output for non‑empty error properties. This way, you can decide whether to continue processing the item or take corrective action (for example, by routing it to an error-handling workflow using a Switch or similar node).

To summarize, nothing is “wrong” with your configuration—the node is behaving as intended under the “Continue (using error output)” option.