Why it matters
After a workflow is published, you need a reliable way to understand what happened when it ran. Workflow monitoring helps you confirm successful automations, investigate failed steps, compare versions, test changes safely, and move workflow configuration between environments when needed.
Use this article after a workflow has been built or published. For workflow creation and publishing basics, use Workflows in Whippy. For configuring triggers, steps, variables, and flow controls, use Build Workflows in Whippy.
Key Concepts
Run: A single execution of a workflow.
Run Status: The result of a workflow run, such as Successful, Failed, Running, or Filtered.
Run Details: The step-by-step execution details for a run, including input, output, console output, and errors.
Version: A saved workflow version.
Draft Version: A version that can be edited before being published.
Current Version: The version currently used when the workflow runs.
Test Run: A run started from a selected workflow version.
Replay: A new run created from a previous run, when replay is available.
Import & Export: Tools for copying workflow JSON out of Whippy or importing workflow steps from JSON.
Open Workflow Monitoring Tools
Inside a workflow, the toolbar gives access to:
Versions: Open version history.
Runs: Open workflow run history.
Import & Export: Open workflow JSON import and export tools.
Some toolbar options are disabled until the workflow has published versions or runs.
Review Workflow Runs
The Runs view shows execution history for a workflow. Use it to confirm whether the workflow is running successfully and to investigate failed or filtered runs.
Step-by-Step: Open Workflow Runs
Open Workflows.
Open the workflow you want to review.
Click Runs in the workflow toolbar.
Select a run from the list.
Review the run status and date.
Open run options when you need more details.
Run Statuses
Workflow runs can show different statuses:
Successful: The workflow completed successfully.
Failed: The workflow encountered an error.
Running: The workflow is still in progress.
Filtered: The workflow stopped because a filter condition intentionally prevented it from continuing.
A filtered run is not the same as a failed run. It usually means the workflow logic stopped the run because the configured criteria were not met.
Search Workflow Runs
Use run search when you need to find a specific execution or value.
Step-by-Step: Search Runs
Open the workflow.
Open Runs.
Enter a search term in Search runs.
Review matching runs.
Open the matching run.
Use Run Details to inspect step-level data.
Search can help locate runs that include specific values, IDs, or text in run data.
Review Run Details
Run Details show what happened inside each step of a run. This is the most useful place to troubleshoot failed workflows or unexpected behavior.
Run Details can include:
Input: The data the step received.
Output: The data the step returned.
Console Output: Logs from code or step execution, when available.
Errors: Error details returned by the step.
Step-by-Step: Inspect Run Details
Open the workflow.
Open Runs.
Select the run you want to inspect.
Open the run options menu.
Select Run Details.
Expand each step to review input, output, console output, and errors.
Use the search field in Run Details to search across step inputs, outputs, and logs.
Identify the first failed or unexpected step.
Update the workflow configuration if needed.
When troubleshooting, start with the first step that has an error or unexpected output. Later failures are often caused by data from an earlier step.
Replay a Workflow Run
Replay creates a new run from a previous run when Whippy has the required trigger data and a published workflow version is available.
Step-by-Step: Replay a Run
Open the workflow.
Open Runs.
Select the run you want to replay.
Open the run options menu.
Select Replay when the option is available.
Confirm the replay.
Review the new run that Whippy creates.
Replay may not be available when the original run is still in progress, trigger data is unavailable, or there is no published workflow version.
Review Workflow Versions
Version History shows draft and published workflow versions. Use it to understand what is currently live, create a draft from an older version, publish a draft, or make a previous version current.
Step-by-Step: Open Version History
Open the workflow.
Click Versions in the workflow toolbar.
Review the list of versions.
Look for the version marked in use to identify the current live version.
Select a version to view it on the canvas.
Version Actions
Depending on the selected version, the version actions menu can include:
Test Run: Start a test run for that version.
Publish: Publish a draft version.
Use this version: Make a published version the active version for workflow execution.
Create Draft: Create a new editable draft from a published version.
Step-by-Step: Create a Draft From a Version
Open the workflow.
Open Versions.
Find the published version you want to use as the starting point.
Open the version actions menu.
Select Create Draft.
Confirm the draft creation.
Edit the draft as needed.
Publish the draft when it is ready to become live.
If a draft already exists, Whippy may ask whether you want to replace the existing draft.
Step-by-Step: Make a Previous Version Current
Open the workflow.
Open Versions.
Find the published version you want to use.
Open the version actions menu.
Select Use this version.
Confirm the change.
Review new runs to confirm the workflow is using the intended version.
Use this carefully because future workflow runs will use the selected version.
Test Run a Version
Use Test Run when you want to run a selected version from Version History.
Step-by-Step: Test Run a Version
Open the workflow.
Open Versions.
Open the actions menu for the version.
Select Test Run.
After the run starts, Whippy opens Runs.
Review the run status and Run Details.
Export Workflow JSON
Export lets you copy workflow JSON for backup, review, or migration.
Step-by-Step: Export a Workflow
Open the workflow.
Click Import & Export in the workflow toolbar.
Open the Export tab.
Review the workflow JSON.
Copy the JSON when needed.
Exported JSON may include workflow configuration details. Treat it carefully and avoid sharing it in places where sensitive workflow data should not be exposed.
Import Workflow JSON
Import lets you paste workflow JSON and save workflow steps into the current workflow.
Step-by-Step: Import Workflow JSON
Open the workflow where the steps should be imported.
Click Import & Export in the workflow toolbar.
Open the Import tab.
Paste the workflow JSON.
Review the import preview.
Fix any validation errors if Whippy shows them.
Click Import and save.
Review the workflow canvas after import.
Reconnect credentials, variables, or app-specific settings if needed.
Test and publish the workflow when it is ready.
Importing workflow JSON can replace or change workflow steps. Review the workflow carefully before publishing imported changes.
Troubleshoot Failed Runs
Use this sequence when a workflow fails:
Open Runs.
Select the failed run.
Open Run Details.
Find the first failed step.
Review the step Input.
Review the step Errors.
Check whether a variable, credential, external API, condition, or missing value caused the failure.
Open the workflow editor.
Update the step configuration.
Test the updated step or run a test version.
Publish the corrected workflow.
Tips and Best Practices
Review runs soon after publishing a new workflow.
Use run search when investigating a specific contact, record ID, email, phone number, or external system value.
Start troubleshooting from the earliest failed step, not the last step.
Use console output to troubleshoot code steps.
Use version history before changing a live workflow.
Create a draft when making meaningful changes to a published workflow.
Test a version before making it current.
Export workflow JSON before making major structural changes.
Review imported workflows for credentials and app-specific fields before publishing.
Troubleshooting
Issue | Possible Cause | Fix |
Runs is disabled | The workflow may not have any runs yet | Publish or test the workflow, then check Runs again |
Versions is disabled | The workflow may not have a published version yet | Publish the workflow to create a version |
A run is marked Filtered | A Filter Step stopped the run intentionally | Review the filter conditions and confirm whether the behavior is expected |
A run failed | A step returned an error or received unexpected input | Open Run Details and inspect the first failed step |
Replay is unavailable | The run may still be in progress, trigger data may be unavailable, or no published version exists | Wait for the run to finish, confirm trigger data exists, and make sure the workflow has a published version |
A previous version should become live again | The current version may contain an unwanted change | Open Versions and use Use this version on the correct published version |
Imported JSON does not save | The JSON may be invalid or missing required step fields | Review the import validation message and correct the JSON |
An imported workflow does not run correctly | Credentials, variables, or app-specific fields may need review | Open each step, reconnect accounts if needed, test the workflow, and publish again |