The Monitoring section in Zoho Flow Settings gives your organisation full visibility into how and when your flows are running. By reviewing the execution history, you can identify failures, inspect the data that passed through each step, and confirm that automations are performing as expected.

Accessing the Monitoring Section

Navigate to Settings in the left-hand menu of your Zoho Flow dashboard, then select Monitoring. The primary tool within this section is the History log, which records every flow execution across your organisation.

Execution History

The History view displays a chronological log of all flow executions within your organisation. Each entry represents a single run of a flow, showing key details such as the flow name, when it ran, and whether it succeeded or failed. This consolidated view makes it straightforward to spot patterns, catch recurring errors, and confirm that scheduled or event-driven flows are triggering correctly.

Step-by-Step Execution Detail

Clicking on any execution record opens a detailed breakdown of that particular run. For each step in the flow, you can view:

• Input data: The values that were passed into the step when it executed.
• Output data: The values returned by the step after it completed.
• Execution status: Whether the step succeeded, was skipped (due to conditional logic), or failed.
• Error messages: Where a step failed, the error message and any relevant response data from the connected application.

This granular view is particularly useful when troubleshooting a flow that is not behaving as expected, as it allows you to pinpoint exactly which step encountered a problem and why.

Filtering the History Log

The History log includes filter options on the right-hand side of the interface. These allow you to narrow down the list of executions to find relevant records quickly. You can filter by:

• Specific flow: View executions for one particular flow rather than all flows in the organisation.
• Execution status: Filter by Successful, Failed, or other status values to focus on runs that need attention.
• Date range: Restrict the log to executions within a specific time window, such as the past seven days or a custom date range.

Practical Uses for the History Log

• Confirm that a newly created flow triggered correctly after its first test event.
• Diagnose why a flow failed by inspecting the input and output of each step.
• Verify that scheduled flows ran at the correct times during the previous period.
• Audit which data was sent from one application to another as part of a specific automation.
• Monitor overall flow health across your organisation to identify any systemic issues with connections or credentials.