Scheduling

Schedules change what Weaver is doing at set times. You can pause downloads during the day, cap speed in the evening, or switch the quota off overnight. Go to Settings → Schedules and click Add schedule.

How A Rule Works

Each rule has:

Time: the time of day it fires, in local time. The default is 08:00.
Days: pick the days it applies to. Pick none to run every day.
Action: what it does. See the table below.
Label: an optional name, like “Off-peak start”.
Enabled: turn a rule off without deleting it.

Most actions also take Several times, a comma-separated list of up to 24 times that replaces the single time.

Rules are grouped by what they control: Downloads, Post-processing, Watch folder, RSS, Speed limit, Hardware profile, Quota metering, and Servers. A rule holds until the next rule in its group fires, even across midnight or across days the rule skips. So one “Pause downloads at 08:00” and one “Resume downloads at 23:00” give you a daytime pause every day. If two rules in a group fire at the same minute, the last one in the list wins.

One-shot actions are different. They do their job once each time they fire and hold nothing.

Deleting a rule changes nothing right away. The queue keeps whatever state it is in.

Actions

Action	What it does
Pause downloads	Pauses downloading.
Resume downloads	Resumes downloading. It also ends a Pause all intake hold.
Pause all intake	Pauses downloads, watch folder scanning, and RSS. Post-processing keeps going. Resume downloads ends it.
Pause post-processing	Running work finishes. New verification, repair, extraction, moves, and scripts wait.
Resume post-processing	Lets waiting post-processing start again.
Pause watch folder scanning / Resume watch folder scanning	Stops or restarts picking up NZBs from the watch folder.
Pause RSS / Resume RSS	No feed is fetched while RSS is paused.
Set a speed limit	Sets speed limits. See Speed Limits.
Switch the hardware profile	Changes the hardware profile until the next profile rule. Only profiles this machine can use are offered.
Set quota metering	Turns quota counting on or off. See Quota Metering.
Set server availability	Turns one server on or off. Weaver saves the change without a connection test and reconnects all servers.
Prune history	A one-shot that clears old history. See Pruning History.

Speed Limits

A speed rule can set three kinds of limit at once:

Global limit: the cap on everything.
Egresses: a cap per egress.
Providers: a cap per server provider.

Values are in MB/s. Leave a field blank to keep that limit as it is. Enter 0 to remove the limit. Fill in at least one field.

Each limit holds on its own. A rule that only sets the global limit leaves the egress and provider limits alone. An egress or provider limit is saved on that egress or provider, the same as if you had edited it under Networking or Servers. A download runs at the lowest of the global, egress, and provider limits that apply to it.

A speed rule takes one time of day, so Several times is not offered. Add one rule per change.

If you delete an egress or provider, the speed and quota rules that name it are removed too.

Quota Metering

A Set quota metering rule chooses between Count downloads against the quota and Stop counting downloads against the quota. Pick Egress to apply it to every egress or to one.

While metering is off, that egress does not count downloads toward its quota and does not refuse work because of it. Its traffic still shows up in statistics.

A rule for one egress wins over a rule for every egress. When you remove the last rule for that egress, it follows the every-egress rule again.

Pruning History

Prune history clears finished entries from History. Choose any of Failed, Completed, and Cancelled. Each has a delete files too option, on by default for failed and cancelled and off for completed.

Two things to keep in mind:

Pruning completed history removes duplicate protection for those downloads.
Deleting completed files also removes the finished output folder.

A prune rule can run at several times, or Every hour at a chosen Minute of the hour.

Removed Actions

0.15 dropped four older actions:

Scan watch folder and Fetch RSS: use the watch folder and RSS pause and resume rules instead.
Run script: scripts now carry their own schedule. See below.
Configured speed limit: use a Set a speed limit rule.

Saved rules that use them are skipped when Weaver starts, with a warning in the log. A pause or resume rule that used to fall back to the configured speed limit gets a global speed rule next to it, pinned to the limit you had saved at upgrade time. If the original rule was off, so is the new one.

Scheduled Script Jobs

Scripts are not scheduled here. A script job with the Schedule trigger has its own run times, days, and Also run at startup option. Set those up under Settings → Scripts → Jobs. See Scripts.

A scheduled job does not start a second run while one is still going. If your computer sleeps through a run time, each job runs its latest missed time once when the clock catches up.

Manual Changes And Schedules

The queue’s Pause all and Resume all use the same pause as schedules. Resume all clears a scheduled pause until the next rule fires.

A speed limit set from the queue takes effect right away, over a scheduled global limit, until the next scheduled speed rule fires. While a schedule is holding the speed down, the speed limit dialog tells you so.

When Weaver Starts

Weaver checks the schedule every minute. When it starts, it replays the schedule first, so each group is set to whatever its latest rule says. New downloads wait for that replay, so a scheduled pause is in place before anything starts.

Time Zone

Schedules use Weaver’s local time. The Docker image runs in UTC unless you set TZ, so add your time zone to the container, for example TZ=Europe/London. See Configuration.

Bandwidth covers speed limits and quotas.
Scripts covers scheduled script jobs.
Advanced Networking covers egresses.
RSS And Watch Folder covers feeds and the watch folder.
Servers covers providers and server settings.