Routines overview
Install catalog health checks, review alerts, run routines now, and optionally build custom scheduled workflows.
Routines are operational monitors and recurring jobs: system catalog templates (report freshness, reconciliation, link health, Creator Connect SLA, and more) plus optional custom canvas routines. They schedule on interval / daily / weekly clocks, open alerts, and can notify, email, fire automation events, or create Pipeline cards.
What you'll do
- Open Dashboard → Routines (feature
routines) - Use tabs: Overview, Installed, Alerts, Catalog
- Install recommended templates; acknowledge or resolve alerts
- Run a routine now; create a custom routine when your plan allows
Before you start
- Plan includes Routines
- Your role can view Routines (and install / run / resolve as needed)
- Marketplace tags and report imports exist if you rely on report-health / reconciliation
- Optional: Pipeline feature enabled if you want alerts as kanban cards
Image placeholder — add `images/overview-cover.png` under this category
Steps
1. Open the Routines control center
- Go to Dashboard → Routines.
- On Overview, review the metric strip: healthy, needs attention, critical, overdue, runs today.
- Use the priority queue for routines in warning/critical state—this is the intervention list, not the full inventory.
- Jump to deep pages when needed: Catalog, Alerts, Mine, System, or New custom.
Image placeholder — add `images/overview-step-01.png` under this category
2. Install from the catalog
- Open the Catalog tab (or Dashboard → Routines → Catalog).
- Browse system templates, for example:
- Report health — marketplace import freshness (required; not pauseable)
- Report reconciliation — map report rows into link analytics
- Link metadata / attribution / marketplace integrity — catalog quality
- Link performance / optimization opportunity watch
- Creator Connect SLA, Price watch, Sponsored Products outcomes
- Install a recommended template. Required system routines stay visible and always on.
- Open an installed routine to tune what the surface allows (thresholds and/or output bindings—alert, in-app, email, automation event, kanban card).
Image placeholder — add `images/overview-step-02.png` under this category
3. Work alerts and schedules
- Open Alerts for open / acknowledged / resolved issues.
- Acknowledge when someone is handling the issue; Resolve when the underlying condition is fixed (for example after uploading a missing report).
- Schedules use:
- Interval — every N hours (1–168)
- Daily — hour/minute (+ timezone)
- Weekly — day of week + time
- Use Run now on templates that support manual runs to verify after a fix.
Image placeholder — add `images/overview-step-03.png` under this category
4. Optional — create a custom routine
- Click Create custom routine (when
custom_routines/ plan allows). - Set name, category (reports, links, creator_connect, ops), and schedule.
- Optionally scope to team, affiliate tag, campaign, or link.
- Build the canvas and output bindings (alert, notification, email, kanban, automation event).
- Save; the routine appears under Installed / Mine and can appear on the Calendar as routine events.
Image placeholder — add `images/overview-step-04.png` under this category
Tips
- Install Report health and Report reconciliation first if you rely on manual marketplace imports.
- Route critical alerts to email + Pipeline operations board so nothing sits only in the Routines UI.
- Pair routine alert triggers with Automations for Slack/Telegram fan-out.
- Required routines cannot be paused—fix data quality instead of silencing them.
- After fixing data, Run now and confirm health returns to healthy on the next evaluation.
Troubleshooting
| Symptom | Likely cause | What to try |
|---|---|---|
| Upgrade block | No routines feature | Billing → upgrade |
| Empty installed list | Nothing installed yet | Catalog → install recommended templates |
| Cannot pause a routine | Required system enforcement | Expected—fix the underlying report/link issue |
| Alert never clears | Condition still true (stale import, bad metadata) | Fix source data, then resolve / run again |
| Custom create blocked | Plan or permission lacks custom routines | Upgrade or ask an admin |
| Kanban output does nothing | Pipeline feature off or board routing disabled | Enable Pipeline; check team routine board settings |