I have a main workflow which trigger an internal workflow via execute workflow node.
I have set error trigger workflow for main workflow as well as the internal workflow.
Even though an error happened in internal workflow, the error workflow linked to internal workflow is not triggering.
Only the main error workflow triggers and treat it as an error happened in Execute Workflow Node.
Is there a way to trigger the internal error workflow when error happened on internal workflow and get the correct error object ?
What is the solution if I specifically want to know that error happened from main or internal workflow
The error trigger isn’t firing at all, even if the true condition fires? One thing to note: the Error Trigger node is designed to get triggered only when the monitored workflow gets executed automatically. This means you can’t test this (to see the result of) an error workflow while executing the monitored workflow manually, in case you did that here when you were testing.
To receive error messages for a failed workflow, you need to select the option Error Workflow in the Workflow Settings of the respective workflow.
Hi @EmeraldHerald Thank fpr quick reply. Let me explain in bit more detail.
The above workflow I attached in the question is parent workflow - its activated and trigger automatically on a message in RabbitMQ .
The ERROR TRIGGER PARENT is configured for this parent workflow’s settings.
If you look in the workflow, there is a node, which is EXECUTE WORKFLOW, which will trigger an internal workflow.
ERROR TRIGGER CHILD is configured in the settings of this internal workflow.
So my expectation was when an error happened in internal workflow, the
ERROR TRIGGER CHILD will trigger first and then ERROR TRIGGER PARENT will be triggered second.
But the actual result is, it trigger only ERROR TRIGGER PARENT and not triggering the other one.
The problem in error object is, it says , lastExecutedNode is “Execute workflow” from parent workflow, so no information about internal workflow is getting here.
Hi @amithr , and thank you for confirming what you’re looking for!
Unfortunately an error workflow won’t give you what you expect here I’m afraid You could however use an HTTP request node in the parent workflow, and then call a webhook node in the child workflow. When done this way, the child workflow execution would be seen as an execution on its own and the error trigger would be called when an error occurs.
That should get you the details and trigger order you want
Welcome to the community 
One thing to note: the Error Trigger node is designed to get triggered only when the monitored workflow gets executed automatically. This means you can’t test this (to see the result of) an error workflow while executing the monitored workflow manually, in case you did that here when you were testing.
You could however use an HTTP request node in the parent workflow, and then call a webhook node in the child workflow. When done this way, the child workflow execution would be seen as an execution on its own and the error trigger would be called when an error occurs.