In a sub-flow, if we set it to run-as user to the user who initiates a session and when the main flow was activated and triggered, the platform cached the flow and an error occurs. When the sub-flows "Run-As" "system" and saved, it doesn't take effect on the flow even though it shows the sub-flow was executed by "system user".

1. Create a Subflow
   
   1. Run As - User who initiates session
   2. Actions – Log info message – “Subflow Test”
   3. Save and publish
2. Create a Flow
   
   1. Run As – System User
   2. Trigger – new incident
   3. Actions –
      
      1. Log info message – “Flow Test”
      2. Add the Subflow from step #1
   4. Save and activate
3. Create an incident to trigger the Flow
4. Flow execution logs will show the Flow was executed by “System User” and the Subflow was executed by the user (Correct Result)

5. System Logs will show the “Flow Test” message was created by “system” and “Subflow Test” was created by the user (Correct Result)

6. Change the Subflow’s “Run As” property to “System User”, save and publish the Subflow
7. Create an incident to trigger the Flow
8. Flow execution logs will show the Flow was executed by “System User” and the Subflow was executed by “System User” (Correct Result)

9. System Logs will show the “Flow Test” message was created by “system” and “Subflow Test” was created by the user (Incorrect Result)

Making changes on the subflow and saving it it is not enough for the changes to apply. The correct process is to also publish the flow one more time after changes are made so they take effect on the following executions.