Skip to main content
Use wait steps to pause a workflow until a time passes or something happens on the ticket, Loop to run steps once for each item in a list, and Goto to go back and run earlier steps again. Every wait step also has Optional Filters. When they don’t match, the wait is skipped and nothing after it on that path runs.

Wait

Use Wait to pause for a fixed amount of time, such as giving a requester a day to reply before a reminder.
  • Duration: how long to wait. The default is 8h. Use units such as 10m, 1h, 2.5h, or 1d, combine them with + and - (for example 1d - 8h), or choose Forever.
  • From Date (optional): the date to measure from. Leave it empty to start counting when the step runs, or pick a date from an earlier step.
  • Timezone (optional): the time zone the wait is calculated in.

Wait Until

Use Wait Until to resume on a calendar date, such as a start date from an onboarding form.
  • Target Date: the date to resume on, either fixed or from an earlier step.
  • Time and Timezone: the time of day to resume, and the time zone it’s in.
  • Date Offset (optional): moves the target date earlier or later. -5d on a start date of March 20 resumes on March 15. +1w resumes a week after.

Wait for Message

Use Wait for Message to pause until someone replies on the ticket, such as waiting for a requester to confirm a fix.
  • Message Authors: the people or groups whose reply counts.
  • Message Sources (optional): count only replies from Web, Email, or Slack. Leave it empty to accept all three.
  • Duration: how long to wait before giving up. The default is 3 days.
Messages written by a workflow or generated by AI never count as a reply.The step always continues. Its Is Success output is true when a matching message arrived and false when the duration passed without one. Put an If / Else on Is Success after it to handle the two cases differently.

Wait for Inactivity

Use Wait for Inactivity to continue only after the ticket goes quiet, such as escalating when nobody has replied for a few hours.
  • Duration: how long the ticket must stay quiet. The default is 8h.
  • Users (optional): only replies from these people reset the clock. Leave it empty to count replies from anyone.
Each matching reply restarts the clock, so the step keeps waiting for as long as people keep replying. It continues once the full duration passes with no matching reply.

Wait for Approval

Wait for Approval pauses until the ticket’s approval finishes, then continues down On Approved, On Declined, or On Timeout. The default timeout is 3 days.
Learn more about approvals in workflows

Loop

Use Loop to run the same steps once for each item in a list, such as messaging every ticket a search returns.Adding a Loop also adds an End Loop step. The steps between them run once per item, one item at a time, with a short pause between items. After the last item, the workflow continues with the steps after End Loop.
  • Collection: the list to go through, from an earlier step. Search Tickets, Search Users, Search Assets, and Search Entitlements all return lists.
  • Limit: the most items to process. The default and the maximum are both 50.
Inside the loop, the value picker offers the current item and Loop Info (the item’s Index, the list’s Size, and the Limit).
If the list is empty, the Loop is skipped, and so is everything after End Loop. Don’t put steps that must always run after a loop over a search that can return nothing.
Steps inside a loop can’t be duplicated, and the Loop and End Loop steps can’t be dragged to reorder.

Goto

Use Goto to send the workflow back to an earlier step and run it again, such as retrying an HTTP request that failed.
  • Step: the step to go back to. It must be upstream of the Goto, so you can’t jump forward or into another branch.
  • Budget: how many times this Goto can jump in one run. The default is 1 and the maximum is 100.
  • Optional Filters: jump only when these match. When they don’t, the Goto is skipped and nothing after it runs.
Adding a Goto also adds an On Limit Reached path. Once the budget is used up, the Goto stops jumping and the workflow continues down that path instead.

Retry a failing request

1

Let the request report failure

Turn off Fail on error on the HTTP Request, so a failed call returns Is Success false instead of failing the step.
2

Check the result

Add an If / Else on the request’s Is Success. Continue the workflow on the True path.
3

Wait, then go back

On the False path, add a short Wait, then a Goto that points at the HTTP Request with a budget of 3.
4

Handle the last failure

On the Goto’s On Limit Reached path, notify your team that the request kept failing.

Skip a wait during a run

Workspace admins can skip a Wait or Wait Until step on a run that’s paused on it, so the workflow continues immediately. Other wait steps can’t be skipped.
Last modified on November 18, 2026