Sub-Workflow and Details of it from Main workflow

Describe the problem/error/question

I’ve got a main workflow with two sub-workflows. Each are added using ‘Execute Workflow’ nodes. Below is a screenshot of how it looks from ‘main workflow’

In case of an error in sub-workflow, is there any chance we can double click or open it to see which sub-workflow failed etc?

So what ideally looking for is (like in Control-M UI)

  • You got the workflow template
  • When an execution runs and it fails, and when you double click on the ‘already executed workflow’, you will be able to see which granular node failed (i.e. within the sub-workflow)

So ideally looking for double-click or zoom in the ‘GET URLS’ in the above example to see the sub-workflow nodes under it. There are a dozen of nodes under the sub-workflow.

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Use the error workflow

There isn’t a way to have that interface of seeing the other workflow by clicking through to it, not as far as i know. But you can set custom error messages and set up error handling.

You can do this using the Stop and Error node.
The Stop and Error node will push an error and you can specify a custom error message, so you can add any information you like. If a Stop and Error happens while being called by another workflow, in the main workflow it will show the Execute Workflow as being failed but it will show the custom error message, so you will know what failed.

You can set custom error messages to be whatever you want. You can also handle errors without needing to stop the workflow if that would be appropriate.

First in the node settings of what might error, set On Error to be Continue (using error output).

That’s what gets you the error legs shown here:

This gives an example of trying to handle an error gracefully with a stop and error as a backup. Instead of sending and email, you can do stuff like substituting default data or retrying.

Or of course you can just error out right away like shown in the http stop and error. If any of these stop and errors are hit, it displays the custom error message set back to your main function

Let me know if that made sense, not exactly the most organized thing i ever wrote

1 Like

thank you Guys. The query was mostly from our operations team who were well familiar with Control-M whereby the tasks can be arranged into a group (similar to sub-workflow), but they can drill down inside and see which one failed etc.

Was thinking if we can raise it as a feature or won’t happen