Journeys

Schedule and control a watched check ​

The schedule starts only after a successful learning run and your approval. Journeys shows when the check will run before you save it.

Choose a schedule ​

In the Start watching or Change schedule dialog, choose:

  • Which days — every day, weekdays, weekends, or individual days.
  • How often — once a day, every 12 hours, or every 6 hours.
  • Time — the whole-hour anchor for the schedule.

The initial suggestion is once a day at 09:00, every day, in the local time shown by your browser. The summary lists the actual run times and an approximate number of checks per month. Review that estimate because each run uses credits.

For a repeating schedule, the selected time is an anchor. For example, an every-six-hours schedule anchored at 08:00 also runs at 14:00, 20:00, and 02:00.

Journeys stores a fixed schedule in UTC and displays it in the current browser's local time. If you view it from another time zone—or your region enters or leaves daylight saving time—the displayed local hour can differ. Use Change schedule if the local wall-clock hour matters.

Run now versus a scheduled run ​

Run starts a manual attempt. It is useful for learning and diagnosis, but it does not change the health strip, last-checked time, or uptime percentage. API, CI, and named-chain attempts are also excluded from those monitoring figures.

Only a scheduler firing answers, “What did this check report at its expected time?” This keeps a helpful retry from rewriting an earlier outage.

Pause and resume ​

Choose Pause on the site page to stop future schedule firings. Pausing keeps the check, schedule, history, variables, secrets, and memory. Choose Resume when it should run again.

Changing a paused check's schedule does not resume it. This lets you prepare a new cadence without accidentally starting monitoring.

Stop watching or delete ​

For a custom check, Stop watching removes its cadence and “Runs after” setting but keeps the editable definition and learned memory as a Draft.

For a catalog check, the corresponding action is Delete check. It removes that catalog check from the site; adding it again later creates a fresh copy without the old values or memory.

A check set to Runs after another check has no cadence of its own. Control the parent's schedule instead, or change the relationship as described in Checks that run after another.