Explains the running user for Schedule-Triggered Flows and provides instructions on how to configure debug logs for troubleshooting errors such as "Apex CPU time limit exceeded."
Schedule-Triggered Flow: A type of platform flow that runs automatically at specified times and frequencies without user interaction. It starts at the scheduled time and processes records in batches. The flow operates in the background and cannot be launched manually.
Running User: The user context under which a flow executes. This determines the flow's access to Salesforce data, including record access and field visibility. The running user's permissions, profiles, and sharing rules impact what the flow can do. For example, if the running user lacks edit permissions for a record, the flow will fail to update it.
When a scheduled flow runs nightly to update records, it executes under the context of the last user who modified the flow, not the record owner. This means the flow's access to records is limited by the permissions and visibility of the modifying user. For instance, if the modifying user lacks access to certain records, the flow will not be able to process those records.
The running user for a Schedule-Triggered Flow determines whose permissions are used to execute the flow and which user must be traced to generate debug logs.
The running user depends on the API version of the flow:
API Version 53.0 and later: The flow runs as the Default Workflow User.
API Version 52.0 and earlier: The flow runs as the "Automated Process" user.
Navigate to Setup | Process Automation | Process Automation Settings.
Check the Default Workflow User field.
When investigating issues like "Apex CPU time limit exceeded," you must set up the debug log for the correct running user.
If the running user is the Default Workflow User, select that specific user in the Traced Entity Name field when creating a new Debug Log configuration.
002471425

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.