Why a workflow does not run or send again

1 min read

Most workflows act once per record. A lead or location that meets the conditions again, or re-enters a status, does not always trigger a second email.

Standard workflows run once per record; Event workflows run once per event

A Standard workflow runs once for each lead or location. It cannot be reset, and a record is not re-enrolled automatically if it meets the conditions again later.

An Event workflow runs each time its event occurs. Many events can happen only once per record, such as the first logged activity, so the workflow runs once. Other events repeat. Each completed web form is a new event, so the workflow can run again every time. If an Event workflow does not run again because its event happens only once per record, send follow-up notifications manually.

For Standard workflows, an enhancement that allows repeated runs is planned but has no release date. Until then, send follow-up notifications manually. This applies, for example, to a second renewal notice or a second approval request.

To check a workflow's type, click Sales > Workflows or Information Manager > Workflows and look at the Type column. The type is Standard, Event or Date. It also appears under the workflow name when you open the workflow. You cannot change the type after the workflow is created. To use a different type, delete the workflow and create a new one.

Campaign actions send once per association (lead, unit, owner)

If a workflow sends a campaign, such as an application and background-check email triggered by a status change, the campaign sends once per lead. Moving the lead out of the status and back in does not send it again.

To make the email send again:

  1. Open the workflow and remove the Send Campaign action.
  2. Add a Send Email action that uses the same email template.
  3. Save the workflow.
  4. Test it with a lead before relying on it.

Renewal workflows triggered by a date

A workflow triggered by the As Of date on the Renewals tab checks every renewal entry on the location daily, not only the latest one.

  • It triggers once per location for a qualifying date.
  • Entries with the same qualifying date do not cause duplicate triggers.
  • Entries with different qualifying dates may trigger separately.

Exit condition keeps locations in an Information Manager workflow by default

By default, a location stays in the workflow after it no longer meets the workflow conditions. To change this, open the workflow, click the Settings tab, and under EXIT CONDITION, select Remove them from this workflow. 

 

For more information, see Stop Information Manager Workflows from Running for Terminated Locations.

Other reasons a workflow does not run

Check these items when a workflow does not run as expected:

  • The workflow is inactive. Open the workflow, click the Settings tab and check that Workflow Status is Active.
  • The record does not meet the conditions. In the Condition section, check that the location matches every condition, such as Lifecycle Stage.
  • The trigger does not match what happened to the record. Check that the trigger (Added, Modified or Added or Modified) fits the change.
  • Existing locations are not included. On the Settings tab, check Execute this workflow for Existing Locations. If it is set to No, the workflow may not run for locations that already exist.
  • Workflow priority. Click Set Priority on the Workflows page and check the workflow order when more than one workflow applies to the same location.
  • The trigger and a modification overlapped. If the workflow was triggered and modified around the same time, the two may have overlapped. If they did not overlap, contact support.
  • The email template or record data. Check that the email template used by the action still exists and that the record has a value in the field the workflow depends on, such as a date.
Was this article helpful?
Your feedback helps us improve our documentation.