By default, Scheduler does not log that a flow has been executed.
The most appropriate method is to output logs using the Logger component in the flow's context.
Alternatively, you can enable logging by setting the following package to the DEBUG level.
<AsyncLogger name="org.mule.runtime.core.internal.context.notification.Policy" level="DEBUG"/>
The following log entries will be recorded.
“resourceId” is the name of the flow.
DEBUG 2025-04-10 18:09:03,627 [[MuleRuntime].uber.11: org.mule.runtime.core.internal.source.scheduler.DefaultSchedulerMessageSource.pollingExecutor - myfirstappFlow/source @2a834d0b] [processor: ; event: ] org.mule.runtime.core.internal.context.notification.Policy: Sending notification: PipelineMessageNotification{action=pipeline process start, resourceId=myfirstappFlow, serverId=shinyas-ltmwgp8.internal.salesforce.com..myfirstapp, timestamp=1744276143627}
005036343

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.