Automation and Flow Logs

Unattended workflows need a record of what they actually did. Automation and Flow logs help the people operating a site confirm that scheduled work ran, understand its outcome, and investigate missing or unexpected files without having watched the work happen.

Begin with the run that should have produced the result. A run summary describes the overall execution, while its individual events and action details show what happened to particular files. Keeping those levels separate helps distinguish a job that never started from a job that ran but could not complete one operation.

For a Sync, review the run's overall outcome before following the relevant file events. For an Automation, use its run record to inspect the actions taken and any errors. When the failure involves a remote system, Outbound Connections provides the corresponding detail about operations against Remote Servers and On-Premise Agents.