Why it matters
Publishing a workflow is the beginning of its operational life. Monitoring shows whether it is starting when expected, following the correct path, and completing its intended actions. Run Details reveal the input, output, logs, and errors available for every executed step so you can find where unexpected behavior began.
Key Concepts
Run: One execution of a workflow.
Run Status: The current or final result of the run.
Run Details: The step-by-step record of inputs, outputs, console output, and errors.
Successful: The workflow completed its active path.
Failed: A step returned an error that stopped the run.
Running: The workflow has not finished, possibly because it is executing or waiting.
Filtered: A Filter Step intentionally stopped the run because its conditions did not pass.
Replay: A new run created from a previous run when replay is available.
Version: The saved workflow configuration used by a run.
Import & Export: Tools for moving or backing up workflow step configuration as JSON.
Open Workflow Runs
Step-by-Step: Review Run History
Open Workflows.
Select the workflow.
Click Runs in the workflow toolbar.
Review recent run dates and statuses.
Select the run you want to inspect.
Open its actions menu when additional options are needed.
Select Run Details.
The Runs option may be unavailable until the workflow has executed at least once.
Understand Run Statuses
Successful: Every step on the active path completed.
Failed: A step error stopped the workflow.
Running: The workflow is executing, delayed, or waiting for an external result.
Filtered: A configured filter stopped the run intentionally.
A Successful status confirms technical completion. Review the outputs when you also need to confirm that the business result was correct.
Search Workflow Runs
Use run search to find an execution containing a specific value, such as a contact identifier, email address, phone number, record ID, or text value.
Step-by-Step: Search Runs
Open Runs.
Enter the value in Search runs.
Review matching executions.
Select the relevant run.
Open Run Details.
Search within the run when that option is available.
Avoid searching with sensitive values in shared environments unless necessary.
Inspect Run Details
Run Details can show:
The data received by each step
The resolved variable values
The output returned by an action
HTTP or app responses
Code Step console output
Filter and condition results
Error messages
Wait or Wait For progress
Step-by-Step: Find the First Unexpected Step
Open the failed or unexpected run.
Start with the trigger and confirm its data is correct.
Move through the executed steps in order.
Compare each step’s Input with what it should have received.
Compare its Output with what the next step expected.
Review Console Output for Code Steps.
Review Errors for the first failed step.
Stop at the earliest incorrect input or output.
Open the workflow draft and correct that step or the mapping before it.
Test the change and publish the corrected version.
Later failures are often consequences of an earlier missing or malformed value.
Diagnose Common Outcomes
A Run Is Filtered
Open the Filter Step in Run Details.
Review the actual input values.
Review each configured condition.
Confirm whether stopping was intended.
Update the filter only if valid events are being excluded.
Filtered is an intentional outcome, not a system failure.
A Run Remains Running
Identify the last active step.
Check whether it is a Wait or Wait For step.
Review the configured duration, callback, polling condition, and timeout.
Confirm the external job or callback still exists.
Allow the wait to complete or correct the draft for future runs.
A Connected App Step Fails
Review the resolved inputs.
Inspect the response or permission error.
Confirm the correct account is connected.
Confirm that account can access the target record, page, channel, or object.
Reconnect the credential if needed.
Test with a safe record.
An HTTP Request Fails
Review the method, URL, headers, and body.
Check whether variables resolved correctly.
Review the returned status and body.
Compare the request with the receiving API’s current requirements.
Correct and retest the draft.
Replay a Run
Replay starts a new execution using data from a previous run when Whippy has the required trigger data and a suitable published version.
Step-by-Step: Replay
Open Runs.
Find the completed run.
Open its actions menu.
Select Replay when available.
Confirm the replay.
Open the newly created run.
Review its status and Run Details.
Replay can repeat real side effects, including sending messages or updating records. Confirm the impact before using it.
Replay may be unavailable when the original run is still active, trigger data is unavailable, or no published version can be used.
Compare the Run with Its Version
When a workflow has changed, confirm which version produced the run. Do not assume an older failure used the current canvas configuration.
Note the run date and version information.
Open Versions.
Review the version that was current when the run began.
Compare its steps with the current draft.
Create or correct a draft based on the appropriate version.
Test and publish the fix.
Export Workflow JSON
Export can provide a backup or help move workflow step configuration.
Step-by-Step: Export
Open the workflow.
Click Import & Export.
Open Export.
Review the JSON.
Copy it to an approved secure location.
Exported configuration may contain identifiers, mappings, or integration details. Handle it according to your organization’s data policies.
Import Workflow JSON
Import can add or replace workflow steps in the current workflow.
Step-by-Step: Import
Open the target workflow draft.
Click Import & Export.
Open Import.
Paste the workflow JSON.
Review the preview.
Resolve validation errors.
Click Import and save.
Inspect the full canvas.
Reconnect or verify credentials.
Review variables and app-specific fields.
Test and publish when ready.
Importing can materially change the workflow. Export the existing configuration first when you need a recoverable copy.
Operational Review Checklist
After publishing an important workflow:
Generate a controlled live event.
Confirm a run appears.
Review its status.
Inspect important outputs.
Confirm messages, records, and external updates reached the correct destination.
Monitor the next several production runs.
Assign an owner for investigating failures.
Review workflows periodically for expired credentials and obsolete logic.
Tips and Best Practices
Review runs soon after publishing.
Start troubleshooting at the earliest unexpected step.
Compare actual run data with test data.
Treat Filtered as a business-logic outcome.
Check the workflow version associated with the run.
Use console output for Code Step debugging without logging secrets.
Confirm side effects before replaying.
Export before major imports or structural changes.
Reconnect and retest integrations after permission changes.
Unpublish a workflow if it is repeatedly causing harmful actions while you investigate.
Troubleshooting
Issue | Possible Cause | Fix |
Runs is unavailable | The workflow may not have executed yet | Publish it and generate a controlled trigger event |
A run is Failed | A step returned an error or unusable output | Open Run Details and inspect the first failed or incorrect step |
A run is Filtered | A Filter Step condition did not pass | Review the filter input and confirm whether the stop was intended |
A run stays Running | It may be executing, delayed, waiting for a callback, or polling | Inspect the active Wait or Wait For step and its timeout |
Replay is unavailable | The run is active, trigger data is missing, or no suitable published version exists | Wait for completion and confirm the workflow has a current version |
The replay repeated an external action | Replay executes the workflow again | Correct any resulting record or message and use safer test data before another replay |
An imported workflow fails | Credentials, variables, or app-specific identifiers need review | Open and test every imported integration step before publishing |
The live workflow differs from the editor | The editor contains a draft while runs use the current published version | Review Versions and publish the intended draft |