Run-As setting is not inherited by subflowsIssue Flow is sometimes executed as system, sometimes as the user initiating the sessionCauseFlow "Run as" setting set as systemFlow is calling subflow whose "Run as" setting set as user. When context gets created by system user itself,it works fine, but if context gets created by other user flow will fail in error state. ****Please note "Created by " field will only indicate who submitted the flow context, this is not the same as "executed as". So in a flow where RUN AS is being set "system", if any user submitting the context the created by will show the user id and in operational view of the flow it will show executed by as "system".ResolutionTo make it consistent, Action should also be set as System, if you want action to be run as system always, that mean both flow and subflow should run as "System"