Automation settings and management

Managing your workflow involves controlling its execution state—Draft, Published, or Paused. Use the header controls to initiate a Test Run for debugging, Publish the workflow to make it live, and monitor performance and errors using the History log.

Automation management gives you full control over the lifecycle of your workflows, from initial testing to real-time, published execution.

Workflow execution states

A workflow can exist in one of three primary states, which dictate whether and how it will respond to a trigger event.

State Status Behavior
Draft Not running The workflow is being built or is inactive. It will not automatically execute when its trigger is activated.
Published (Live) Running The workflow is active and in a production state. It will execute indefinitely in real time whenever its trigger condition is met.
Paused Temporarily suspended The workflow was previously published but has been temporarily deactivated using the toggle. It will not execute until it is resumed.

Managing workflow execution

The main controls for managing your workflow’s state are found in the header of the workflow editor.

Start a test run

A Test Run is the most critical step before publishing a workflow, allowing you to confirm that the entire sequence of Triggers and Actions is configured correctly without affecting live data unnecessarily.

  • Execution: A test run executes the workflow only once when the button is clicked.
  • Purpose: It validates the logic, confirms connections to external services, and generates the necessary sample data for all nodes.
  • Re-testing: To run the test again, you must re-visit the workflow and click the Start test run button again, as it does not automatically re-run.

Publish / go live

When you are confident in your workflow’s configuration and testing, you can make it live.

  1. Click the Publish button in the workflow editor header.
  2. The workflow is now in the Published (Live) state.
  3. It will run indefinitely every time its associated trigger condition is met.

Pause and resume

Once a workflow is published, you can temporarily suspend its execution without unpublishing it entirely.

  • Click the toggle switch (which will be marked Published) in the header to set the workflow to the Paused state.
  • To resume the workflow, click the toggle switch again. The workflow will immediately return to the Published (Live) state and begin listening for triggers.

Monitoring workflow history

The History tab is your primary tool for monitoring your automation’s performance and debugging issues once it is live.

The history provides a comprehensive log of all workflow execution attempts, displaying:

  • Status: Whether the run was successful or unsuccessful (failed).
  • Run Messages: Detailed messages that help you understand what happened during the execution. If a failure occurred, the message will often pinpoint the node and the reason for the error, allowing you to quickly identify and fix the problem.

Regularly checking the history ensures your automations continue to function as expected and helps you maintain the health of your database processes.

Related content

Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions; we’re ready to assist you.