Scheduling a workflow
Schedule a clinical workflow in Rhazes to run automatically in your own timezone, and pause, edit or remove that schedule later.
Updated
Setting one
A workflow can run on its own, repeating as often as you need, in a timezone you set. That timezone matters: a workflow due at 8am should run at 8am where you work, not where a server is.
The workflow shows its next run time. Check it says what you expected before leaving it running, because a schedule that is an hour or a day out will not announce itself.
Pausing and resuming
A schedule can be paused without being deleted, and resumed later. Right for annual leave, or while you are changing a workflow you do not want firing mid-edit.
Pausing is better than deleting for anything temporary, because the schedule and its settings survive.
Editing one
The timing can be changed without rebuilding the schedule. If a sweep is landing at a time you never read it, move it rather than working around it.
Removing one
Deleting a schedule stops the workflow running automatically. The run history is kept, so removing a schedule does not lose the record of what it did while it was running.
What to schedule
The work that gets skipped when a shift is busy: the weekly list review, the outstanding results check, the follow-ups nobody has chased. A schedule does it whether or not anyone remembered.
Do not schedule anything you have not run by hand and read in full first. See Running a workflow.
Check on them
A scheduled workflow that has started failing looks exactly like one that is finding nothing, because both are silent. Look at recent runs occasionally rather than assuming silence means success. See Following a Rhazes workflow run.