Arbor Workflows: Delay Step

The Delay Step pauses workflows for a relative period or waits until a specific date. Use it for onboarding, admissions, absence management, and other timed tasks. Authorised users can advance active delays manually; afterward, workflows continue to the next action.

 

The Delay Step will delay your workflow for a period of time. Arbor Workflows can either pause for a fixed time period, or it can wait until a specific date. Whether you need to pause for a few days before sending a follow-up or wait until a specific date, the Delay Step allows you to do this.

 

Pause vs. Wait: What's the Difference?

While both terms sound like they do the same thing, they handle time and action differently. 

 

Pausing for a Set Period of Time

How it works: The workflow stops and rests for a dynamic, relative duration (e.g., 3 hours, 5 days, or 2 weeks) starting from the time the workflow hits that step.

The benefit: It dynamically adapts to the workflow.

  • Example — New Staff Onboarding Feedback: When a new staff record is created in Arbor MIS, a workflow triggers. You want to ask them how their first week went, but not the second they walk through the door.

    The Setup: You add a Delay step configured to Pause for 7 days.

    How it runs: If Teacher A starts on a Tuesday, the workflow pauses for 7 days and sends their feedback form the following Tuesday. If Teacher B starts on a Friday, it pauses for 7 days and sends theirs the following Friday.

 

You can also change the Unit of time. Select the dropdown to change the unit of time.

 

Waiting Until a Specific Date

How it works: The workflow waits until a specific calendar date before proceeding, regardless of when it arrived at that step.

The benefit: It ensures that no matter when individual workflows are kicked off, the next action happens at a defined date. That date could be fixed for all workflows, or it could be based on Dynamic data referencing an early data point in the workflow.  

  • Example — September Term Prep & Welcome Packs: Parents of new students submit their enrolment forms throughout June, July, and August. You want to send them their final "First Day of Term" checklist email at the exact same time.

    The Setup: You add a Delay step configured to Wait until September 1st.

    How it runs: Whether a parent submits their enrolment form on June 15th or August 20th, their specific workflow will halt at that step and wait. The system will release the welcome email to all parents on September 1st.

 

 

When to Use a Delay Step

Adding a delay is perfect for handling time-sensitive school processes without needing manual reminders. Common examples include:

  • New Staff Onboarding: Wait 5 days after their start date before automatically triggering a check-in form.

  • Admissions Follow-ups: Send an automated email confirmation immediately, wait 3 days, and then trigger a checklist for the admissions team to review documents.

  • Absence Management: Delay a notification to the senior leadership team until 2 hours after a staff absence is logged, giving the cover manager time to arrange a solution first.

  • Any 'timed' communications and tasks. 

 

Frequently Asked Questions

Can I cancel a delay while a workflow is actively running?

If a workflow is currently paused on a Delay Step, users with permissions to see, review, and amend workflows can view the active workflow status and manually push it to the next step if needed.

What happens if a delay is followed by a human step?

The delay will pause the entire workflow. Once the delay timer ends, the workflow will move to the next step for example, sending a Decision (Approval) request or a Form to a human user's task list.

Was this article helpful?
0 out of 0 found this helpful
I'm still stuck!

Comments

0 comments

Article is closed for comments.