A run is one checklist executed against one site. Runs store step status, API results, notes, and timestamps.
Start a run
| Method | Where |
|---|---|
| Push Checklist | Sites row (single site) |
| Run Checklist wizard | Batch Run → first tab |
| Quick Launch | Dashboard (site + checklist) |
| Onboarding | Optional first run after connect |
When starting a run, the hub typically pushes a snapshot to the client panel so clients can work immediately.
During a run
On the hub (Batch Run)
- Advance API steps automatically or step-by-step.
- Mark manual steps complete from the hub if needed.
- Mark not complete to revert a manual step.
- View step notes and attachment thumbnails.
- Refresh Client Panel to re-send snapshot and sync bundle (Pro).
On the client site
- Complete manual steps in the panel.
- Add notes (required text) and optional media library screenshots.
- Use deep links to open the right admin screen.
Hub and client stay aligned: client toggles call back to the hub; the hub returns an updated snapshot for the panel.
Run statuses (conceptual)
- In progress — steps remaining.
- Completed — all steps done.
- Failed / cancelled — depending on execution and your process.
Batch runs
Batch Run → Batch Queue: same checklist against multiple sites queued and processed in order. Useful for monthly maintenance across a fleet.
Run history
- Sites → expand a site row → run history (checklist, progress, dates, user).
- Archive hides a run from default lists; delete removes it permanently (capability required).
Drift (configuration checks)
Some workflows include drift verification—comparing remote configuration to expectations. Manual verify lives under Batch Run → Drift Monitor. Scheduled drift is Pro-only and opt-in in Settings.