Skip to content

queues subscriptions create: --source-type choice list omits browserRun #166

Open

Description

@MattieTK

Summary

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:

cf queues subscriptions create \
  --name browser-run-crawl-events \
  --source-type browserRun \
  --events crawl.started --events crawl.updated --events crawl.finished \
  --destination-type queues.queue \
  --destination-queue-id <QUEUE_ID> \
  --enabled

Expected request body (from --dry-run):

{
  "name": "browser-run-crawl-events",
  "source": {
    "type": "browserRun"
  },
  "destination": {
    "type": "queues.queue",
    "queue_id": "<QUEUE_ID>"
  },
  "events": ["crawl.started", "crawl.updated", "crawl.finished"],
  "enabled": true
}

Reproduction

cf queues subscriptions create \
  --destination-type queues.queue \
  --destination-queue-id 00000000000000000000000000000000 \
  --source-type browserRun \
  --events crawl.started \
  --name test-sub \
  --enabled \
  --dry-run

Actual output:

┌ Error
│ Invalid values:
│ Argument: source-type, Given: "browserRun", Choices: "images", "kv", "r2",
│ "superSlurper", "vectorize", "workersAi.model", "workersBuilds.worker",
│ "workers.script", "workflows.workflow"
└

For more information, run cf queues subscriptions create --help

Docs impact

Found while migrating the Queues event subscriptions documentation to cf:

  • src/content/partials/queues/event-subscriptions/browser-run-events.mdx (rendered on /queues/event-subscriptions/events-schemas/)

Environment

  • cf: 1.0.0-rc.2
  • Node.js: 24.22.3
  • OS: macOS 26.7.3 (arm64)

Activity

  1. petebacondarwin commented on Nov 20, 2026

    @petebacondarwin
    Contributor

    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"}.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions