question Re: How does the flow context relationship is working? in Platform Analytics forum

How does the flow context relationship is working?

SHREEDHARANM — Sat, 21 Mar 2026 14:41:09 GMT

Hi Community,

I am looking for a deep-dive technical explanation or official documentation regarding the lifecycle relationship between a Parent Flow and an Asynchronous Subflow.

The Scenario:

A Parent Flow calls a Subflow.

The "Wait for completion" checkbox is unchecked (False).

The Parent Flow moves to the next step and enters a "Waiting" state (e.g., waiting for a record update).

The Subflow also enters a "Waiting" state (e.g., a timer or a wait for condition).

The Observation:

When the Parent Flow Context is cancelled manually or through any script, the Subflow Context is also being cancelled automatically, despite being triggered asynchronously.

I would appreciate any insights from those who have explored the sys_flow_context hierarchy in detail and helping me to understand this in detail

Re: How does the flow context relationship is working?

Tanushree Maiti — Sat, 21 Mar 2026 15:09:57 GMT

Hi @SHREEDHARANM

Follow this KB or SN doc links . Hope it will help you.

1. KB2565934:How to show subflow stages in a parent flow

2. https://www.servicenow.com/docs/r/zurich/build-workflows/workflow-studio/show-subflow-stages-in-a-parent-flow.html

3. https://servicenowguru.com/graphical-workflow/applying-sync-async-pattern-flow-designer/#:~:text=To%20make%20this%20Subflow%20run%20Asynchronously%2C%20make%20sure%20that%20the,Flow%20on%20Incident%20Comment'%20Flow

Re: How does the flow context relationship is working?

SHREEDHARANM — Sat, 21 Mar 2026 15:17:07 GMT

Thanks for your response @Tanushree Maiti

Re: How does the flow context relationship is working?

SohamTipnis — Tue, 24 Mar 2026 07:14:50 GMT

Hi @SHREEDHARANM,

In ServiceNow, even when Wait for completion is false, the subflow is only asynchronous in execution, not independent in lifecycle.
It still runs as a child context of the parent in sys_flow_context.
So both parent and subflow remain part of the same execution hierarchy.
When the parent flow is cancelled, the engine automatically cascades cancellation to all child contexts.
This includes subflows, even if they are in a waiting state.
Async just means non-blocking, not detached.
To make it fully independent, you need to trigger it via FlowAPI or events, not a direct subflow call.

Let me know if this

If you find my answer useful, please mark it as helpful and correct. ‌‌‌‌‌‌‌‌‌‌‌😊

Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10