Create Accountor Login
Docs

Waiting Until Something Is True or Happens

Part of the MountDev Ops Workflows documentation. Updated November 19, 2026

MountDev Ops Workflows documentation | Updated November 19, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

What They Are

Wait used to hold a run for a time. It now has three choices when you add a step:

  • Wait for a Time. What Wait has always done: from 1 second to 30 days, until a time of day, or until a date (How Workflows Run).
  • Wait Until Something Is True. Reads something every so often and goes on when it is true, such as "the site is ready" or "the document was received".
  • Wait for Something to Happen. Holds the run until an event from one of your apps arrives, such as "A Visit Was Added".

Both new steps hold the run without using any work while they wait. Each ends with a plain result that a later Check Something can read. The existing Wait keeps its name in saved workflows and in the API.

Wait Until Something Is True

SettingWhat it isStartRange
Read ThisOne action that only reads, with its inputs. Inputs can use values from the run.NoneAn action that only reads, with no flag
Go On WhenOne check on what the read answered: a value, then is, is not, is more than, is at least, is less than, is at most, or is there, and what to compare with (typed, or a value from the run)NoneThe checks Check Something has
Check EveryHow often to read5 minutes60 to 3,600 seconds
Give Up AfterHow many checks at most, and optionally a date from the run24 checks1 to 500 checks, and never longer than 30 days in all
If It Never HappensGo On (the run goes on and a later step decides) or Fail the RunGo OnTwo choices

The actions you can read are Get a Record, Find Records, and each of your own Connection Actions that is a read (a GET with no flag) (Connection Actions). An action that changes, deletes, spends, or emails is refused when the workflow is saved. A read runs as the same person, with the same permission and field rules, as a Do Something step with that action. A read you may not make is refused at save, and a field that is hidden from that person is never in the answer, so it is never compared, not even with "is not".

A Connection Action answers with status (the number the service replied with), ok, and bytes, and with each Keep Value you named. Name the value you want to check something other than status, such as site_status, and check that.

How it runs:

  1. The first check is made as soon as the step starts. If it is already true, the run goes on at once.
  2. Otherwise the run waits (Waiting | checked 3 of 24 | next check 2:35 PM) and checks again every so often.
  3. The step ends when the check is true, when the last check or the date passes, or when you stop the run.
  4. It hands on met (yes or no), timed_out (yes or no), checks (a count), and the read's own kept values from the last check, so a later step can use them. The run log keeps only met, timed_out, and checks.
  5. A check that cannot be made is not a retry of the step. A read that fails (the service is busy, an answer is not understood) counts as a check that was not true. Three failed reads in a row end the step with "The check could not be made 3 times in a row." Asking again never uses up the step's retries.

Wait for Something to Happen

SettingWhat it isStartRange
EventAny event an app declares, from the same list as When Something Happens in One of Your AppsNoneOne event
Only WhenUp to 3 checks on the event's values (is, is not, is one of), each compared with a typed value or a value from the run, so "the order is this run's order" worksNoneValues the event declares
Wait At MostHow long to wait7 days1 minute to 30 days
Remind EveryA reminder to named people while waitingOffOff, or 1 to 30 days, up to 5 people
If It Never HappensGo On or Fail the RunGo OnTwo choices

How it runs:

  1. The wait begins when the step begins and sees events from that moment on. It never looks back at an event that came before it started. To catch something that may already be true, put a Wait Until Something Is True before it.
  2. When an event of that type arrives, your account's waiting runs for that event type are checked, each one's Only When is checked, and the matching waits end. Delivery is at least once, so each wait ends exactly once, and the same event delivered twice ends it once.
  3. It hands on event_id (a number), timed_out (yes or no), waited_seconds (a count), and the values the event declares. The run log keeps only the number, the count, and yes or no.
  4. A wait never starts a run. An event made by a workflow's own change can end a wait, because ending a wait only lets an existing run go forward. The rule that a change a workflow made never starts a workflow is unchanged, so a workflow still cannot loop.
  5. Only When on a record's fields is read as the person who turned the workflow on. If that person lost access, or the field is hidden from them, the check does not pass. A workflow you only run by hand and have not turned on can wait, but a check on a record's fields will not pass until it is turned on.

Reminders

While the run waits, the people you named get the existing Workflow Notice on the bell every N days: "Still waiting for A Visit Was Added, day 3", with the workflow's name and the step's label. A reminder never holds a record, a value, or a name from the event. It is never an email, and it goes only to people on your own team, so it can never be a message to a client. A reminder to someone who is not on your team is refused when the workflow is saved. Reminders stop when the wait ends or the run stops.

What It Costs

Waiting counts nothing. Each check of a Wait Until that calls an action counts 1 in Background work, as every step that does something does, and a failed read counts too. Wait for Something to Happen counts 0. The estimate before you turn a workflow on shows a Wait Until as "Up to 24 checks", and Test Run says "at most 24 counted checks".

Limits

  • At most 1,000 runs may be waiting in these two steps at once in your account. Past that, a new wait fails its step with "Too many runs are waiting. Try again later." and nothing else is affected.
  • These limits are data, the same for every account, and can be changed by the provider: check every 60 to 3,600 seconds, up to 500 checks, never more than 30 days in all, wait for an event 1 minute to 30 days, reminders every 1 to 30 days for up to 5 people, and 3 checks in Only When.
  • Neither step can go inside a Branch or a Repeat. A run waits in one place at a time.

Stopping, Changing, and Restarting

  • Stop This Run ends the wait at once and the run as Stopped. No check is made after that.
  • Turning the workflow off or changing it does not end a run already waiting. A run keeps the steps it started with.
  • Waits are kept in your account's own data, so a stopped instance resumes them from the stored next check, with the same number of checks made.
  • A run that failed in one of these steps can be run again from the step that failed (Workflow Reliability). The wait starts over, and the checks already made stay counted.

Test Run

Test Run describes both steps and waits for nothing. A Wait Until's read runs once only if the action has a test mode; otherwise it is only described. Wait for Something to Happen needs no event.

Turning on and AI Agents

Everything is saved off, and only a person turns a workflow on. A change an AI agent saves to a workflow that is on turns it off. Turning one on through your AI agent waits for an owner or admin, and the request describes each waiting step in words: what it reads and how often, or which event and for how long, and who is reminded. Neither step can spend money, delete data, or email a client, and no key goes in a workflow. An AI agent cannot end a wait or send a reminder.

What Is Kept

Waits are in Export Everything (Workflow Waits). A wait keeps its counts and times, never a key. A run keeps only ids, counts, and true or false.

For AI Agents

workflows_catalog lists the two step types (wait_until and wait_event), which actions a Wait Until may read (waits.reads), the checks, the limits, and each event with the values it declares (only_when.events). workflows_save accepts both steps and always saves them off. workflows_test describes them and the most checks they could count. workflows_runs shows a waiting run's progress as counts (waiting).

{ "id": "ready", "type": "wait_until", "read": { "action": "northwind_hosting.get_site", "inputs": { "site": "{{steps.make.site_id}}" } },
  "when": { "value": "site_status", "op": "eq", "to": "ready" }, "every_seconds": 300, "max_checks": 24, "if_never": "go_on" }

{ "id": "visit", "type": "wait_event", "event": "crm.contacts.created",
  "only_when": [ { "value": "status", "test": "is", "to": "Lead" } ],
  "wait_seconds": 604800, "remind_days": 2, "remind": [ 3 ], "if_never": "go_on" }

Ask Us Anything

We’d love to hear from you!