A flow calling a child flow that is switched off

Flow calls a child flow that is turned off.

An enabled flow declares a Run a Child Flow call to a flow that is turned off. A child flow that is off does not start when called, so on any run reaching the call the parent gets nothing back and the work the child was written to do does not happen. The platform gives no warning when a child is switched off while parents still point at it.

Pathix reads the call in the parent's own definition. It does not watch runs, and a definition does not record whether a call sits on a branch that is ever taken, so this reports a declared call to something switched off rather than an observed failure. A flow that was never turned on and one somebody switched off look the same from here, so the finding says only that it is off. One finding per calling flow, naming every turned-off child it calls.

List the Run a Child Flow actions across your enabled flows, collect the child flows they name, and check each child's state. Any child that is off is the finding. Doing this from exported definitions is far faster than opening each flow, and there is no built-in screen that relates parents to children.

Turn the child flow back on and confirm it has its connections, or remove the call from the parent. Check which other flows call the same child first, because one child flow is usually shared.

This one is environment health, so it carries a plain label and no control mapping. Presenting an operational gap as a security finding would make the real security findings harder to trust, so we keep the two apart.

• A plugin step that re-triggers itself on every save
• A cloud flow that re-triggers itself on every run
• Two plugin steps at the same execution order writing one column
• Two flows writing the same column on the same trigger