Knowledge Base

Topics
Where to find the delay feature
How to use the delay feature
What you can add after the delay
How to cancel a pending workflow
How many delays can I use in a workflow?
What can disrupt the delay feature?

Workflow automation: delay feature

SR
Steven Reinartz, September 15, 2022

When using automations, there are times when you will want to have an automated step performed at a later time or date, as opposed to being performed immediately.

With the delay feature for the workflow automation tool, you can set up actions to be performed automatically and at your preferred time and date.


Where to find the delay feature

When you create your automation, you will start by choosing a trigger event (e.g., deal created).

Once you have selected your trigger event, you will see three options for the next step: condition, action, and delay:


How to use the delay feature

Once you have located the delay feature, you can start adding time delays into your automated sequences. You will have two options for how to configure your delays – predefined and custom:

  • Predefined will allow you to select options like a day of the week or a default number of hours or days.
  • Custom will allow you to input a specific number and unit of time.

What you can add after the delay

Once you have added your delay step and specified the time that must elapse, you will then be able to add an action, condition, or even another delay as the next step in the automation:


Condition

If you add a condition step after your delay, the automation will wait the selected amount of time and check to see if the condition in question has been met. For example:

The deal owner condition will be checked after one minute has passed. If the condition is met after that time, the automation will proceed to its next step. If the condition is not met after that time has passed, the automation will be stopped.

Action

If you add an action step after your delay, the automation will wait until the selected amount of time has passed, and then the specified action will be performed. For example:

The ownership of the deal will be changed to the selected user after one minute has passed.

Delay

If another delay step is added directly following a previous delay, the time will be added to the previous delay.

For example, if you add a one-day delay step followed by a one-hour delay step, you'll have a delay of one day and one hour.


How to cancel a pending workflow

There are two ways you can cancel pending workflows.

  • The first is to go into the automation and deactivate it, which you can do from either the editing view or the automation list view, then save. This will prompt a window, giving you the option to either maintain or cancel your pending executions:
  • The other way to accomplish this is by making a change to either the trigger, condition, or action within your automation. After doing so, you will see a different prompt:

If you check “Cancel all pending executions”, any pending actions will be stopped. If you leave the box unchecked, pending actions will continue to fire after those changes are made.

Note: You can deactivate workflow automations from the editing screen or the list view

How many delays can I use in a workflow?

The number of delays per workflow is dependent on your plan:

AdvancedProfessionalEnterprise
30 active workflows per user60 active workflows per user100 active workflows per user
10 actions per workflow10 actions per workflow10 actions per workflow
3 delays per workflow 10 delays per workflow 10 delays per workflow
Total Time Limit: 90 daysTotal Time Limit: 90 daysTotal Time Limit: 90 days

The total time allocated to delays in your workflow cannot surpass 90 days. Meaning you can, for example, have one delay with 90 days or 6 with 15 days each.

Note: When you choose the option to skip weekends, the weekend days will still count toward the 90-day limit.

What can disrupt the delay feature?

There are select instances where changes made to a workflow containing delays will require the additional removal of steps within that workflow.

Past tense operators

Adding a delay before a condition with reference to the past will lead to all steps following the delay being deleted:

A workaround is to modify the condition first so that no past references are configured and, only after that, add the delay.

Note: After a delay step, all operators that reference the past are NOT available in conditions (“Was”, “Was not”, etc.)

Deleting delays preceding “change” conditions

When a workflow contains has changed/has not changed/has changed to conditions and they come after a delay, if the delay is deleted, there is no support for those comparators anymore. An example of this would be if you have a has not changed condition set to be assessed three days after a deal is created:

In this case, if you remove the delay step, what you are left with is a deal created trigger event that has a has not changed condition. This is not possible since changes in a deal cannot be assessed if the deal was just created.

Was this article helpful?

Yes

No

Related articles

Got any questions?

Contact us