I have a screen flow that displays Account fields dynamically based on the Type of account the user selects. The user then makes selections on the screen and saves the changes. I am trying to create an automation that would clear all of the user's previous selections if the Type of account is changed. I thought a subflow would be a workable solution, so I created a record-triggered flow (to be used as the sub-flow) with the AccountID variable available for input. When I try to call the record-triggered flow using the subflow element it is not populating in the 'Referenced Flow' search box. Trying to figure out why that is. Thanks!
Visual Workflow – Trouble Connecting a Subflow to a Main Flow
subflowvisual-workflow
Related Solutions
After several hours of scouring the interwebs, with no reason to believe this should not work, I finally uncovered why I was getting this error. In short, it was because of a private setting on my sContact sObject variable from the main Flow.
The reason this was not easily detected, my sContact variable was created from a "Get Records" component like so. Unfortunately when using the "Automatically store all field" feature there is no way to add the "input/output" classification (yet...vote here)
The Flow Metadata Documenation lists the various run modes (runInMode)
The context that the flow runs in. Valid values are:
DefaultMode — How the flow is launched determines whether the flow runs in user context or in system context. In the UI, this value appears as User or System Context—Depends on How Flow is Launched.
SystemModeWithSharing — The flow respects org-wide default settings, role hierarchies, sharing rules, manual sharing, teams, and territories. But the flow doesn’t respect object permissions, field-level access, or other permissions of the running user. In the UI, this value appears as System Context with Sharing—Enforces Record-Level Access.
The doc seems to be missing the latest addition which is SystemModeWithoutSharing.
However, going off the above and your specific scenario - the warning can be ignored. While it's technically true that the runInMode is mismatched, how the flow is run in default mode determines the context and, in your example (record-triggered), that would be System Mode (as the other answer notes) which matches your subflow's context.
For other situations, this warning may be useful if the flow is being run in a different manner which would cause the resolved contexts to mismatch.
Best Answer
A subflow must be autolaunched type or screen flow type, not record-triggered type. See documentation: