# Display Parent Workflow Execution Link in Sub-Workflow Executions

**URL:** <https://community.n8n.io/t/display-parent-workflow-execution-link-in-sub-workflow-executions/226141>\
**Category:** UI\
**Created:** [November 25, 2025, 1:50am UTC](https://community.n8n.io/t/display-parent-workflow-execution-link-in-sub-workflow-executions/226141 "2025-11-25T01:50:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Scott\_Francis](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/scott_francis/32/139950_2.png) [@Scott\_Francis](https://community.n8n.io/u/Scott_Francis)\
**Post date:** [November 25, 2025, 1:50am UTC](https://community.n8n.io/t/display-parent-workflow-execution-link-in-sub-workflow-executions/226141/1 "2025-11-25T01:50:17Z")

</div>

When viewing the execution details of a workflow that was triggered as a **Sub-Workflow** , n8n currently does not show which parent workflow initiated it. This makes it difficult to trace execution flow, understand context, or perform debugging across chained workflows.

I am requesting a feature that adds the Parent Workflow Execution ID (with a clickable link) to the Sub-Workflow execution view.

**Why this is useful**

- **Improved traceability:** Quickly see which workflow triggered the sub-execution without digging through logs or searching manually.

- **Faster debugging:** When troubleshooting execution issues, it’s essential to follow the chain from parent → sub-workflow → child executions.

- **Better observability for complex automation:** Many n8n setups use orchestration workflows that call multiple sub-workflows. This feature would make it significantly easier to monitor and audit execution paths.

- **Parity with other automation tools:** Many workflow/orchestration platforms expose call-chains to improve visibility.

### **Proposed behaviour**

- In any Sub-Workflow execution, show a small section such as:  
” **Triggered by:** Workflow _Name”_  
” **Parent Execution:** `#123456"` (clickable link to parent execution)
- Display this near the top of the execution details for easy visibility.

### **Impact**

This simple addition dramatically improves the user experience when working with multi-workflow architectures, especially those using reusable workflows, orchestration patterns, approval flows, or complex agent-based systems.