You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
queues subscriptions create: --source-type choice list omits browserRun #166
cf queues subscriptions create --source-type restricts the value to a choice list that does not include browserRun, even though Browser Run crawl event subscriptions are documented and supported by wrangler queues subscription create <QUEUE_NAME> --source browserRun.
Users subscribing a Queue to Browser Run crawl events (crawl.started, crawl.updated, crawl.finished) currently have to drop down to a raw JSON --body payload. This mirrors open issues cloudflare/cf#179 (artifacts / artifacts.repo) and cloudflare/cf#262 (email.sending).
Expected behaviour
browserRun should be included in the --source-type choice list for cf queues subscriptions create:
Confirmed that the Queues backend accepts source.type: "browserRun" for account-level crawl subscriptions. No source-specific selector is needed, and the supported events are crawl.started, crawl.updated, and crawl.finished.
The published OpenAPI schema omits browserRun, so cf rejects --source-type browserRun before sending the request. An upstream schema fix is in review. This issue will stay open until cf picks up the published schema and regenerates the command.
In the meantime, omit --source-type and pass the full JSON request with --body, including "source": {"type": "browserRun"}.
Activity
petebacondarwin commentedon Nov 20, 2026
Confirmed that the Queues backend accepts
source.type: "browserRun"for account-level crawl subscriptions. No source-specific selector is needed, and the supported events arecrawl.started,crawl.updated, andcrawl.finished.The published OpenAPI schema omits
browserRun, socfrejects--source-type browserRunbefore sending the request. An upstream schema fix is in review. This issue will stay open untilcfpicks up the published schema and regenerates the command.In the meantime, omit
--source-typeand pass the full JSON request with--body, including"source": {"type": "browserRun"}.