A pipeline that only runs when you press Execute is half-finished. Schedule runs it on its own — every day at six, every hour, every weekday — using the same pipeline, with nothing to change in it. This level schedules the World 5 inbox project to run every morning.
Goal
A schedule that runs w5-5-inbox-project every day at 06:00 in your time zone, which you can
pause, resume and trigger on demand.
You'll need
- The
w5-5-inbox-projectpipeline from level 5.5 (it's fine if its inbox is empty — an empty inbox is a normal day). - About 15 minutes.
Steps
1. Open Schedule
Editor menu ▸ Schedule. The Job Scheduling page lists every schedule in the project, with two tabs: All schedules and My alerts (level 7.3).
2. Create the schedule
Click + New Schedule. In Create Schedule:
| Field | Value |
|---|---|
| Target Type | Pipeline |
| Select Pipeline | w5-5-inbox-project |
| Schedule | Visual Builder · Daily · Run every day at 06:00 |
| Timezone | your own — it's pre-filled from your browser |

Under the builder, Backend Cron Output shows the cron expression it produced: 0 6 * * * — minute
0, hour 6, every day. The Timezone decides whose 06:00 that is. Leave Start and End
empty; they're for schedules that should only run inside a window.
Save.
3. Read the list

- Schedule shows the cron.
- Next run is shown in your browser's time zone. If the schedule's zone is different from yours, the time you see here is converted — a 06:00 Lisbon schedule appears as 07:00 to someone in Berlin.
- Status is Active. That badge is also a button: click it and the schedule becomes Paused — it keeps its settings and just doesn't fire. Click again to resume.
- Double-click a row to edit the schedule — its cron, time zone or start/end window.
4. Run it now
Hover the row and press ▶ — Run now. The pipeline runs immediately, regardless of the time, and the run appears in Monitor like any other. Use it to test a schedule without waiting until tomorrow.
5. Cron for everything else
Visual Builder covers daily, hourly, weekly, monthly and every-N-minutes. For anything else, switch to
Advanced (Cron) and type the five fields yourself — minute hour day-of-month month day-of-week:
| Cron | Runs |
|---|---|
0 6 * * * |
every day at 06:00 |
*/15 * * * * |
every 15 minutes |
0 9 * * 1-5 |
09:00, Monday to Friday |
30 2 1 * * |
02:30 on the 1st of every month |
The scheduler checks for due schedules every 30 seconds, so a run can start up to half a minute after the exact time.
Expected result
w5-5-inbox-projectis listed with0 6 * * *, status Active, and a next run at the coming 06:00 (converted to your browser's time zone if needed).- ▶ adds a new run to Monitor.
Common pitfalls
It ran an hour early (or late). The schedule's Timezone isn't the one you meant — UTC is a common leftover. Double-click the row and fix the time zone rather than shifting the hour, or daylight saving will move it again in spring.
Nothing ran overnight. Odara runs schedules while the Odara server is running. On a laptop that sleeps, nothing fires; for real schedules, Odara lives on a machine that stays on.
The schedule fires, but the data is old. The schedule only decides when. If the pipeline reads a file that wasn't replaced, it happily processes yesterday's file again. That's what alerts on rows (next level) are for.
Paused by accident. The status badge is a toggle; one click pauses. If a schedule "stopped running", check its status first.
What you built
A pipeline that runs every morning on its own. The next level makes sure you hear about it when it doesn't go well — and, just as important, when it "succeeds" with nothing in it.
Check yourself
One question, drawn from a larger bank. Get it right to pass.
Nothing ran overnight on a laptop that was asleep. Why?