Skip to main content

​
Stream Setup

​
Why does stream validation fail?

Common causes are:
  • URL is not currently live (NOT_LIVESTREAM, STREAM_OFFLINE)
  • URL format is invalid (INVALID_URL)
  • Stream cannot be fetched (STREAM_FETCH_FAILED)
Start with Validate Stream, then see Debugging Playbook.

​
Which stream types are supported?

  • YouTube Live
  • Twitch live channels
  • RTSP and RTSPS sources

​
Conditions

​
Why does my condition never trigger?

Most misses come from vague wording. Use strict yes/no language and visible criteria. Use this loop:
  1. Test with Check Once
  2. Refine condition text
  3. Re-run monitor job
Reference: Writing Reliable Conditions

​
Jobs

​
Why did my job stop?

Jobs can end because the condition was met, max duration was reached, the job was cancelled, or an error occurred. Inspect current and final state with Get Job Details.

​
How do I continue coverage after a job ends?

Create a new monitor or digest job when the previous job reaches terminal state. Implementation patterns:

​
How do I cancel a running job?

Use Cancel Job with the job_id.

​
Delivery Modes

​
Should I use polling, webhooks, or SSE?

  • Polling: simplest for backend scripts.
  • Webhooks: best for event-driven systems.
  • SSE: best for real-time UI streaming.
Decision guide: Choose Your Workflow

​
Reliability

​
What is the fastest troubleshooting loop?

  1. Validate Stream
  2. Check Once
  3. Get Job Details
  4. Debugging Playbook
Also see: Debugging Playbook

​
Next Steps