Omniscio

Run if missed (cron catch-up)

A per-job switch, off by default, that makes a cron job catch up once when Omniscio was closed across its scheduled time — instead of quietly skipping the missed fire as it does today. Covers where the toggle lives, why every missed window collapses into a single run, the seven-day limit, and what a catch-up run still respects.

On this page

What it is

Omniscio's cron scheduler only fires a job when Omniscio is actually running at the scheduled minute. If your laptop was asleep, Omniscio was closed, or you were away for a few days, a job scheduled for "every day at 9 AM" simply doesn't run for the days Omniscio was off — by default Omniscio notices the missed fire, writes a log note, and quietly moves the schedule forward to the next future run without running it. (That default is deliberate: it stops a job that was missed hundreds of times from firing hundreds of times the moment you open the app.)

Run if missed is a per-job toggle, off by default, that changes that one decision for the job you turn it on for: when Omniscio was closed across the job's scheduled time, the job runs once the next time you open Omniscio, catching up misses from the last 7 days.

This is the catch-up behavior Windows Task Scheduler calls "Run task as soon as possible after a scheduled start is missed" — now available on Omniscio's own cron jobs, so you get Omniscio's friendly schedule presets, AI-by-chat scheduling, inbox failure alerts, and self-healing without having to split your automations between Omniscio and Task Scheduler.

One exception you do not have to opt into: a session's own wake

A session wake — the "wake me at 15:10" a session arms for itself, including the check-in beats between crew members — never needs this toggle. When the app is restarting as a wake's time comes up, the boot pass re-arms that fire so it arrives once as soon as the app is ready, and writes it into the schedule's run history. A restart spends most of its time before the new process is even running (the old one shutting down, then the rebuild), so the fire would otherwise be lost in that gap with nothing recording it.

The line is recency: a wake fire that is at most 30 minutes old is delivered; an older one is treated like any other missed window — not re-fired, because a beat that late is stale — but it is still written to the run history, marked as dropped, so you can see it happened. Ordinary jobs are unaffected and keep the behavior described here.

Where to find it

It is not a global switch — it belongs to one job. Open the Cron Jobs view from the Cron row in the sidebar, click the job you want, and Run if missed sits in that job's editor alongside the other per-job toggles. Tick it and save; the setting is stored with the job and travels with it.

How it behaves

How to use it

  1. Open the job's editor. In Omniscio's Cron Jobs virtual project, click any job to bring up its editor dialog. "Run if missed" lives below the other per-job toggles in the same form.
  2. Flip on "Run if missed." The row is labelled Run if missed with the description "If Omniscio was closed at the scheduled time, run once on next open (catches up misses from the last 7 days)." Off by default — existing jobs keep their current behaviour until you opt in.
  3. Save. That's it. The next time you open Omniscio after a missed fire, the job runs once within about a minute of launch.

The toggle is hidden for one-time jobs ("run once at a specific date/time"). A one-off has no recurring schedule to resume, so catch-up doesn't apply to it — only recurring and limited (run-N-times) jobs show the toggle.

What to expect

  • One catch-up run, not one per missed day. However many scheduled fires were missed while Omniscio was closed — three days of a daily job, a whole weekend of an every-5-minutes job — the job runs exactly once on next open. All the missed windows collapse into that single catch-up, then the schedule resumes normally from the next future time. So the "an every-minute job would fire hundreds of times" worry doesn't happen.
  • Only misses from the last 7 days catch up. If a job was missed longer ago than a week (an automation that lay dormant while you were away for two weeks), it is not caught up — it just resumes on its normal schedule, same as the default. The 7-day window covers a long weekend or a normal vacation without resurrecting something stale.
  • It respects everything a normal run respects. The catch-up run goes through Omniscio's normal scheduled-run path, so:
    • Approval still applies. If the job requires approval, the catch-up run waits in your inbox for your tap, exactly like a normal fire — it is never auto-fired around the gate.
    • It won't double-run. Omniscio's at-most-once guards apply, so a catch-up can't fire the same job twice.
    • Cost applies once. For paid jobs (ones that run a recipe or spawn a Claude session), the catch-up is one billable run, not one per missed window. If you opt several paid jobs into catch-up and you've been away a while, expect each to fire once when you open Omniscio — that's the intended behavior of opting in.

The surrounding cron machinery — how jobs are created and what the engine's regular tick does — is on the create a cron job with AI page. Its sibling opt-in, which repairs a job after it fails rather than after it is missed, is cron self-healing, and what you see when a run fails for good is on cron failure alerts.

Last verified 2026-09-28