Campaigns and recurring operations
Published: 2026-08-12
Run one operation across many routers over days, picking up offline devices automatically when they return.
A normal operation needs your routers online right now. But your sites lose power, and half the fleet may be dark when you press the button. Campaigns exist for exactly that.
What a campaign is
One operation run across a group of routers, staying alive for days (up to 30). Online routers are done immediately; offline ones are stored as waiting targets and picked up automatically the moment they return — with no action from you and no re-running the campaign.
How it works
- You choose the operation, the routers, and how long the campaign lives.
- You type one confirmation for the whole campaign.
- It runs one router at a time, and preflight is re-run for each device at the moment it executes — not when the campaign was created.
- It closes itself early once every target has settled.
The verdicts you will see
- Succeeded — the change was applied and proven.
- Nothing to do — the device is already in the desired state. This is not a failure, and it is very common on a fleet that is already partly configured.
- Waiting to return — the device is still offline. Also not a failure.
- Failed — refused, or could not be proven; the reason is shown per device.
At the end you get a report naming any devices that were never reached.
Recurring operations
Scheduled repeat runs — for read operations only (full diagnostic, update checks). Changes are deliberately not schedulable: a change needs a person reading its result and confirming it.
When to use which
- Single operation — one or two devices, right now.
- Campaign — a change you want across the fleet, and you accept it taking days.
- Recurring — periodic monitoring with no change.