Scheduled tasks
Ask once. Get the answer every week.
A schedule reruns a saved collector with its parameters and output definition. It reuses the agent’s plan, so you do not pay for it to think the source through again. Basic schedules are in the first release. Richer change tracking follows.
Controls
What you set.
- Frequency and timezone.
- Per-run and monthly spending limits.
- Snapshot, append new records, or update matching records by a key.
- Where the result goes after each run.
- Notifications: completion, meaningful change where supported, or failure.
- Pause, resume, edit, or delete at any time.
Your table · 4 rows shownIllustrative
| rundate | rowsnumber | newnumber · derived | changednumber · derived | gonenumber · derived | statustext |
|---|---|---|---|---|---|
| 2026-09-16 | 120 | 0 | 2 | 0 | complete |
| 2026-09-15 | 120 | 1 | 0 | 1 | complete |
| 2026-09-14 | 118 | 0 | 0 | 0 | partial · 3 pages timed out |
| 2026-09-13 | 120 | 0 | 4 | 0 | complete |
Behavior
What happens between runs.
Early access
Have a question you ask every week?
Tell us the sources, how often they change, and where the answer should land.