Skip to main content

Troubleshoot Automation Workflows

Find out what to check if your Prospect CRM workflow won't save, start, send emails or do what you expect.

H
Written by Heather

If an Automation Workflow in Prospect CRM isn't behaving as you expect, these checks cover the most common causes. You need to be a CRM Admin to edit and manage workflows.


Fix common problems

Find your problem in the list, then follow the check shown.

Workflow not starting

Check it's been published and the header shows Enabled, not Draft or Disabled. Check the record matches the trigger's filter. For Quote Chase, check the template you sent is selected in Triggered By Templates.

Can't save, test or publish

Look for steps marked Needs setup, and finish setting them up.

Emails failing

Check the triggering record has a Contact with a valid email address, or set the To field in the Send Email step.

A step ran but didn't do anything

Open the step and check it's fully set up. Not every incomplete step shows Needs setup. For example, an Add Tag step with no tag chosen doesn't show the label.

Runs ending earlier than expected

The filter is checked before each step. If a record stops matching the filter, the run ends. Check your filter conditions.

Date waits not updating

Inferred Wait Until dates aren't recalculated if the field changes after the step starts waiting.

A workflow run has failed

Open the run in Run History, fix the cause shown in the Failure Reason, then retry it. See View run history and manage runs.


Follow best practice

These habits help you avoid problems before they happen.

  • Test before you publish. Use a test record you control, as non-email actions really happen during tests.

  • Use filters to stop runs. Because the filter is checked before each step, adding conditions such as Status is Open automatically ends chasers once a Quote is won or lost.

  • Use the Else path for 'everything else' instead of a path with no conditions.

  • Keep loops within the limit. Loops are limited to a maximum of 5 repeats per Loop step to prevent workflows running forever.

Did this answer your question?