Unverified50% confidenceFactExact time
The Error Trigger's trigger condition is "the entire execution failed", not a single node reporting an error; if a node error is caught and handled by Try Catch, the execution does not terminate in an error state, and the Error Trigger will not fire.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
n8n Error Handling: Error Trigger vs. Try-Catch — How to Choose
youtubeCodeFlow AI Automation10/18/2026
Related Entities
Related Claims
UnverifiedThe reason the loop stopped was not that it was discovered or intercepted, but that the runner eventually crashed due to malformed output, pushing the task into an error state.71% similarUnverifiedFail-open means the system chooses to let the operation through when a security mechanism fails; fail-closed means it blocks by default when it fails.69% similarUnverifiedUsing the failed_loops counter as the sole alert condition is wrong: if the scheduler does not start the worker process, the counter will stay flat and look like a healthy state, i.e. "zero failures may also mean zero work".66% similarUnverifiedThe common failure chain StareBrain reconstructs is: Agent dispatches an action → the dispatch times out before arrival is confirmed → the system does not see the SUCCESS marker → it is judged as a failure → a retry is triggered → the second dispatch produces a duplicate.64% similarUnverifiedThe four tool call 'timeout' failure modes include: the client actively aborts the call, the server returns an error result (isError: true), the framework converts the call into a background task and returns a task id, and idle abort.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1061694API
curl https://kongchang.com/api/v1/knowledge/claims/1061694MCP
get_claim(id=1061694)