Run workflows on a schedule
The Scheduler tab runs a saved .weave workflow at a time you choose, with
no need to open it and press Run. Use it for a nightly refresh, a morning
report, or a one-off run at a set time.
Scheduled jobs run inside the EdgeWeave app. If EdgeWeave is closed when a job is due, the run is skipped (a run up to five minutes late is still started). Leave the app open, or minimised, for jobs that matter.
Create a job
-
Open the Scheduler tab.
-
In New Scheduled Job, give the job a Name.
-
Pick the Project and the .weave file to run. Only workflows that exist in that project are listed.
-
Choose how often it runs:
Mode Use it for Once One run at a date and time Daily Every day at a time Weekly Chosen weekdays at a time Monthly A day of the month at a time Advanced A cron expression, for example */15 9-17 * * mon-frifor every 15 minutes during working hours on weekdays -
The form shows the next runs it will produce, so you can check the schedule before you save.
-
Press + Create Job.
Manage jobs
Each job in Scheduled Jobs shows its project and file, the next run time and the result of the last run (Success, Failed, or Never run).
- Run Now starts the job immediately, in addition to its schedule.
- Disable and Enable pause and resume it without losing the schedule.
- History lists previous runs with their status. Open a run to read its log, including any error message.
- The bin icon deletes the job.
A Once job that has already run stays finished: disabling and re-enabling it does not run it again. Use Run Now for a deliberate repeat.
Runs and concurrency
A scheduled run executes the workflow the way Run does, without opening a tab, so anything the workflow does (saving files, writing to a database, calling a model) happens as usual. A run is marked Failed if it ends with an error; the history log shows why.
Only one scheduled run executes at a time by default; other due jobs wait their turn. Change this in Settings > Scheduler > Max concurrent scheduled runs.
Tips
- Test the workflow with Run in the editor first, then schedule it.
- Use Run Now and the history log to confirm a new job works before relying on its first scheduled run.