Validating workflows

Edit online

To check that all required components, such as authentications and action blocks, are in place before you run your workflow, you can validate it. Validating your workflow helps to ensure fewer runtime errors and smoother workflow performance.

The process identifies potential issues, such as missing authentications, misconfigured blocks, or incomplete inputs, and provides actionable feedback with suggested fixes directly in the editor. By validating your workflow and implementing the suggested fixes, you can ensure fewer runtime errors and save time.

Take note of the following aspects of workflow validation:
  • Workflows are automatically validated when opened.
  • Validation does not prevent you from saving or running the workflow.
  • The validation option is unavailable while the workflow is running or when the AI assistant is generating the flow.
  • You can click Validate at any time to revalidate before running the workflow.

Procedure

  1. Open the Workflows page and select the workflow that you want to validate.
    • The workflow is validated automatically before the workflow editor opens.
    • If issues exist, you see Errors and Warnings indicators next to the Validate button.
  2. Click the Errors or Warnings indicator to open the Workflow validation panel.
    • The panel lists issues with descriptions and suggested actions.
    • Use Go to block to find the affected block in the workflow.
  3. Update block data or configurations to fix issues.
  4. Click Validate (or Revalidate) again to confirm that issues are resolved.

Validation issue types

The validation process identifies the following types of issues in your workflow:

  • Errors (blocking issues): you must resolve these issues to minimize the chances of workflow execution failures.

    Examples: Missing required fields, non-existing authentications, missing action or meta blocks.

  • Warnings (non-blocking issues): you can resolve warnings to improve workflow efficiency and reduce potential inconsistencies.

    Examples: Invalid required parameters or inputs, syntax errors and potential configuration inconsistencies.