Which Endpoints Create Jobs
These endpoints create async jobs:POST /live-monitorPOST /live-digest
GET /jobsGET /jobs/{job_id}DELETE /jobs/{job_id}
Lifecycle States
| Status | Meaning |
|---|---|
pending | Job accepted, not yet running |
running | Job actively processing |
completed | Job finished successfully |
stopped | Job stopped without failure (cancelled, timed out, or ended) |
failed | Job ended due to processing/runtime error |
Typical Lifecycle
- Create job (
live-monitororlive-digest) - Receive
job_id - Observe
running - Reach terminal state:
completed,stopped, orfailed
Common Stop Reasons
You can inspect stop context in Get Job Details. Common reasons include:- condition detected (
completed) - max duration reached (
stopped) - max windows reached for digest (
stopped) - manual cancellation via
DELETE /jobs/{job_id}(stopped) - stream or processing failure (
failed)
Time-Bounded Runs
Monitoring jobs are time-bounded. Design your workflow to start a follow-up job when terminal state is reached if continuous coverage is required.Operational Pattern
- Create job
- Store
job_id - Track status (polling, webhook, or SSE)
- Handle terminal state
- Recreate job if coverage must continue
Next Steps
- Polling implementation: Use Polling
- Push delivery implementation: Use Webhooks
- Field semantics in responses: Get Job Details