A schedule runs one of your processes automatically, on a recurring basis, without you clicking Start process yourself. A scheduled run creates a normal run exactly like a manual one — see Monitor and manage a run in DQE One Standalone for what happens from there.
Where to schedule a process
- Scheduler in the left navigation (has its own + quick-add icon), or the New scheduler button on the Scheduler page itself.
The Overview page's Schedule Jobs widget lists your 5 soonest schedules (Name, Frequency, Next run date).
Its edit icon opens the process, not the schedule — to change a schedule's frequency, date or time, go to the Scheduler page instead.
This is a separate mechanism from a process's own Auto-start the next step after completion option (see Create and launch a process in DQE One Standalone) — that chains one of your processes right after another finishes; it doesn't involve a schedule at all.
Create a schedule
On the New Scheduler screen, fill in:
- An Active / Inactive switch — defaults to Active.
- Name — a name for the schedule itself.
- Process — pick from your own, non-archived processes.
- Frequency — one of: Every 15 minutes, Every 30 minutes, Every 45 minutes, Every hour, Every day, Every week, Every month, Every year.
- Date — can't be earlier than today.
- Time — picked from Hour / Min / AM-PM wheels; minutes are limited to :00, :15, :30 or :45.
Click Create (or Save when editing an existing schedule). All five fields are required. You can create more than one schedule for the same process.
Nothing checks that the process is actually ready to run. If you schedule a process that's still a draft or missing required setup, every run it fires will simply fail until you finish configuring the process.
How the recurrence works
There's no separate "day of week" or "day of month" field — the recurring day comes from the Date you pick for the first run: Weekly repeats on that same weekday, Monthly on that same day-of-month, Yearly on that same day and month.
For Every hour/day/week/month/year schedules, pick a time on the hour (:00). After the first run, later occurrences land back on the hour regardless of the minutes you originally chose. Only the Every 15/30/45 minutes frequencies keep firing at your exact minute every time.
What happens when it fires
A scheduled run is created and goes through the same statuses as a manual one, and shows up on the process's Results screen exactly the same way — there's nothing on screen that marks a run as "scheduled" versus "manual".
If the process reads from SFTP and no matching file is found when the schedule fires, the run still ends up Failed with the usual error message — see "Getting notified" below for the one way this case is treated differently.
Tracking your schedules
The Scheduler page's Incoming tab lists Name, Process, Frequency, Next Run and Status.
Frequency here shows the raw value you picked (e.g. "hour"), not the friendly label from the form (e.g. "Every hour"). Status is the schedule's own Active/Inactive state — not the outcome of its last run. For that, use the History tab (the same run history described in Monitor and manage a run in DQE One Standalone — scheduled runs appear there identically to manual ones).
While editing an existing schedule, a History button also opens a side panel listing that process's most recent runs directly on the same screen.
Pausing a schedule
Switch it to Inactive and save. Switch it back to Active to resume it.
There's currently no way to delete a schedule from the app — use Inactive instead of looking for a delete option.
If the scheduled process uses a Rules Set (Unify Process or Index Records), creating the schedule locks that Rules Set from further edits for as long as the schedule exists — and since schedules can't be deleted, that lock can't currently be lifted from the app either. Think it through before scheduling this kind of process if you still expect to tune its Rules Set afterwards.
When a schedule gets paused automatically
The app itself switches a schedule to Inactive, without asking, in two cases: you change anything in the scheduled process's own configuration, or you restore that process from the archive. Nothing on screen tells you this happened — no banner, no email.
After editing a process that has an active schedule, get in the habit of checking its Status on the Scheduler page — don't assume it's still Active.
Getting notified about a scheduled run
Scheduled runs use the same My Account → Notifications per-process-kind preference as manual ones (see Monitor and manage a run in DQE One Standalone) — the same success/failure email you'd get from starting the process yourself.
For Every hour/day/week/month/year schedules (not the 15/30/45-minute ones), you'll also get a reminder email about an hour before the run, naming the process — gated by that same Notifications preference.
One exception: if a scheduled SFTP run fails only because no new file was found to process, you won't get the usual failure email for it — you'll still see it as Failed if you check the Results screen or Run History.
Limits
Only Processes can be scheduled — DataPipelines can't be scheduled yet.
When you reopen an existing schedule to edit it, double-check the Date and Time shown before saving — they may not match your own timezone. Saving without adjusting them could silently shift when the schedule actually runs.
Related to