Skip to main content

Execution Monitoring

What you'll learn
  • How to access workflow execution history using the workflow_history button
  • How to read execution logs and check success or failure status
  • How the log level setting affects the detail of execution records
  • How to troubleshoot failed workflow executions

Execution monitoring lets you track every time a workflow runs, see whether it succeeded or failed, and inspect the details of each step. This is essential for verifying that your workflows are functioning correctly and for diagnosing issues when something goes wrong.

Accessing execution history​

To view the execution history for your workflows:

  1. Navigate to Automacoes > Workflows in the sidebar to open the workflows list page.
  2. Click the workflow_history button at the top of the list page.

This opens the execution history view, which shows a log of all past workflow executions. Each entry in the history includes information about when the workflow ran, which workflow it was, and whether the execution was successful.

What execution records show​

Each execution record in the history typically includes:

  • Timestamp -- The exact date and time the workflow ran
  • Workflow name -- Which workflow was executed
  • Status -- Whether the execution completed successfully, failed, or is still in progress
  • Trigger data -- What event or condition started the workflow
  • Step-by-step results -- The outcome of each individual step in the workflow, so you can see exactly where things succeeded or went wrong

How log level affects execution detail​

The Nivel do Log (Log Level) setting on each workflow controls how much detail is captured in the execution records. This is configured in the workflow form when you create or edit a workflow.

  • Higher log levels capture more detailed information about each step, including input values, output values, and intermediate data. This is very helpful during development and testing.
  • Lower log levels capture only essential information like success/failure status. This reduces noise and storage once a workflow is stable and running in production.
tip

Set the log level to a higher (more verbose) setting while you are building and testing a new workflow. Once the workflow is running reliably, reduce the log level to keep your execution history clean and manageable.

Troubleshooting failed executions​

When a workflow execution fails, follow these steps to identify and fix the issue:

  1. Open the execution history by clicking the workflow_history button on the workflows list page.
  2. Find the failed execution in the list. Failed executions are typically marked with a failure status indicator.
  3. Inspect the step results to find which step failed. The execution record shows the outcome of each step in sequence, so you can pinpoint exactly where the failure occurred.
  4. Review the error details. Depending on the log level, the record may include error messages, the data that was passed to the step, and other diagnostic information.
  5. Fix the issue in the workflow. Common problems include:
    • Incorrect {{variable}} placeholder names that do not match available data
    • Missing required fields in a step configuration
    • External services (webhooks) that are unavailable or returning errors
    • Invalid data formats passed between steps
  6. Re-test the workflow after making your fix. For manual workflows, use the executeManual button. For hook workflows, trigger the relevant event again. For temporal workflows, wait for the next scheduled run or adjust the schedule.

Best practices for monitoring​

  • Check execution history regularly during the first few days after activating a new workflow. Early detection of issues prevents problems from compounding.
  • Use the Debug all button (Depurar tudo) in the Etapas section of the workflow form to test your workflow before activating it. This catches many issues before they appear in production.
  • Adjust log levels as needed. Increase verbosity when troubleshooting a specific issue, then reduce it once the problem is resolved.
  • Review the workflows list periodically to ensure all enabled workflows are running as expected, using the filter and history tools on the list page.
info

The workflow_history button on the workflows list page gives you a centralized view of all executions across all workflows. This makes it easy to spot patterns, such as a workflow that fails every time it runs, or one that has not executed in a long time.

Next steps​