Once you've implemented the workflow logic, you can perform a test run to ensure it executes as intended. Following successful testing, you can proceed to publish the workflow, allowing it to execute within the production environment.
Test Runs
Before publishing a workflow, you can test it by clicking Test Run at the top right of the screen. Choose from the previous trigger events to simulate realistic data.
When testing your workflow, you may want to skip the execution of certain steps because they are time-consuming, require a user's reaction, the access to the service is limited and so on. In such cases, you can use one of the following options:
Mock outputs simulate step execution without triggering actual API requests, offering preconfigured responses for testing.
Initiate test runs of workflows from a selected step, eliminating the need to execute the entire workflow each time you want to test a specific section.
Production Executions
Once the workflow is published (read more about workflow states), it will run in the production environment based on the trigger event. These are additional execution options for published workflows:
Monitor Workflow Executions
You can monitor both test and production executions. In instances of failures, the step that led to the workflow failure will be highlighted. To locate specific steps, use the search in the toolbar at the bottom of the screen.
Monitor all workflow executions by using the Activity Log.
Review past and ongoing executions of a specific workflow in the Run Log, accessible from the designer.
The Run Log displays up to 30 of the most recent workflow executions within the last 7 days. Check the Activity Log for the full workflow activity record.
