When workflows do not behave as expected, use these techniques to diagnose and fix issues.
View workflow runs
Every workflow execution creates a run record:
Open the workflow
Navigate to Automations and select your workflow.
View runs
Open the runs view to see execution history.
Select a run
Click on a specific run to see details.
Review execution
See which actions ran, what data was used, and any errors.
Run statuses
| Status | Meaning |
|---|
| Active | Workflow is currently executing |
| Finished | Workflow completed all actions |
| Failed | An error stopped the workflow |
Common issues
Workflow not triggering
Symptoms: Workflow never runs when expected.
Check:
- Is it published? Unpublished workflows do not run.
- Are conditions too strict? Review trigger conditions to ensure they match your records.
- Is the trigger correct? Verify the trigger type matches the event you expect.
- Is the event happening? Confirm the triggering action is occurring in Slant.
Fix:
- Publish the workflow if it is not yet active
- Simplify or remove trigger conditions to test
- Verify the correct trigger type is selected
Wrong data in actions
Symptoms: Tasks have wrong names, emails go to wrong people.
Check:
- Are variables correct? Verify variable names match available data.
- Is the right record in scope? Check what the trigger provides.
- Are variables resolving? Look for literal variable text (e.g.,
{{household.name}} appearing as-is) that was not replaced.
Fix:
- Correct variable names (e.g.,
household.name not name)
- Use the variable picker instead of typing manually
- Verify the trigger provides the data you need
Action fails
Symptoms: Run shows failed status with an error on a specific action.
Check:
- What is the error message? Click on the failed action in the run view.
- Is required data missing? Some actions need specific inputs.
- Does the record exist? The record may have been deleted after the trigger fired.
Common errors:
| Error | Cause | Fix |
|---|
| Record not found | Referenced record was deleted | Check if the record still exists |
| Required field missing | Action is missing a required input | Add the required value |
| No household | Workflow expected a household but none was available | Verify the trigger provides a household record |
Branch not taking expected path
Symptoms: Workflow follows the wrong branch.
Check:
- Review conditions — Are they evaluating as expected?
- Check data values — What values does the record have?
- Logic operators — Is the AND/OR logic correct?
- Branch order — Branches are evaluated in order; the first match wins.
Debug:
- Add an internal notification at the start of each branch to see which fires
- Check the run details to see condition evaluation results
Workflow stops at find opportunity
Symptoms: Workflow stops partway through without an error.
Cause: The Find opportunity action halts the workflow if no matching opportunity exists for the household.
Fix:
- Verify the household has an opportunity in the expected pipeline
- Consider adding a Create opportunity action before the find
Debugging techniques
Add notifications
Insert internal notification actions to trace execution:
Trigger
-> Notification: "Workflow started for {{household.name}}"
-> Action 1
-> Notification: "Action 1 complete"
-> Action 2
Test with specific records
Use a test client to verify behavior:
- Create a test client with known data
- Trigger the workflow on that client
- Verify results match expectations
- Adjust and repeat
Check run data
In the run details, you can see:
- Trigger data — What triggered the workflow
- Action results — What each action produced
- Errors — Any error messages
- Duration — How long the run took
Simplify the workflow
If a complex workflow fails:
- Create a copy of the workflow
- Remove actions until it works
- Add actions back one at a time
- Identify which action causes the issue
Retry failed runs
Some failures are temporary. To retry:
Find the failed run
Open the workflow and navigate to its runs.
Select the run
Click on the failed run.
Retry
Click Retry to re-execute the workflow from the failed action.
Manual recovery
If a workflow fails mid-execution:
- Check which actions completed in the run details
- Manually perform any skipped actions
- Fix the workflow configuration to prevent future failures
If a workflow made unwanted changes (e.g., added wrong tags or sent incorrect emails), you need to manually undo those changes. Check the run details to see what the workflow did.
Preventive measures
Test before publishing
- Save the workflow without publishing
- Test on a single record
- Verify results are correct
- Then publish
Start with fewer actions
- Begin with 1-2 actions
- Verify they work
- Add complexity gradually
- Test after each addition
Monitor regularly
- Check runs periodically for failures
- Review workflows when your processes change
Getting help
If you cannot resolve an issue:
- Capture the error — Note the workflow name, run details, and error message
- Document the problem — What you expected vs. what happened
- Contact support — Provide the workflow name and run ID
Next steps
