Cloudflare Browser Rendering Crawl not working

Workers

BUG: /browser-rendering/crawl endpoint returns "Crawl job not found"

Project: Cloudflare Browser Rendering
Issue Type: Bug
Priority: High
Component: Browser Rendering — /crawl API
Labels:

browser-rendering

browser-rendering

crawl

crawl

api

api

async-jobs

async-jobs

---

Summary

The newly released

/browser-rendering/crawl

/browser-rendering/crawl

endpoint (announced March 10, 2026) accepts POST requests and returns a valid UUID, but subsequent GET polling to retrieve results consistently fails with error code 1001 ("Crawl job not found"). The async job backend does not appear to be processing or storing crawl jobs.

---

Environment

| Field | Value |
|---|---|
| Plan | Workers Paid ($5/mo) |
| Browser Rendering status | Active (102 successful

/content

/content

Steps to Reproduce

1. Send a POST request to the crawl endpoint:

POST /browser-rendering/crawl
Content-Type: application/json

{
  "url": "https://example.com/",
  "limit": 1
}

POST /browser-rendering/crawl
Content-Type: application/json

{
  "url": "https://example.com/",
  "limit": 1
}

2. Receive a successful response:

{
  "success": true,
  "result": "<uuid>"
}

{
  "success": true,
  "result": "<uuid>"
}

3. Poll the crawl status endpoint:

GET /browser-rendering/crawl/<uuid>

GET /browser-rendering/crawl/<uuid>

4. Receive an immediate failure response:

{
  "success": false,
  "errors": [
    {
      "code": 1001,
      "message": "Crawl job not found"
    }
  ]
}

{
  "success": false,
  "errors": [
    {
      "code": 1001,
      "message": "Crawl job not found"
    }
  ]
}

5. Continue polling every 2 seconds for 30+ seconds — response never changes.

---

Expected Behaviour

The GET request should return one of:
- A pending/in-progress status while the crawl is running
- The completed crawl results once finished

---

Cloudflare Developers•2w ago

Maverick

Cloudflare Browser Rendering Crawl not working

Workers

BUG: /browser-rendering/crawl endpoint returns "Crawl job not found"

Project: Cloudflare Browser Rendering
Issue Type: Bug
Priority: High
Component: Browser Rendering — /crawl API
Labels:

browser-rendering

browser-rendering

crawl

crawl

api

api

async-jobs

async-jobs

---

Summary

The newly released

/browser-rendering/crawl

/browser-rendering/crawl

Environment

| Field | Value |
|---|---|
| Plan | Workers Paid ($5/mo) |
| Browser Rendering status | Active (102 successful

/content

/content

Steps to Reproduce

1. Send a POST request to the crawl endpoint:

POST /browser-rendering/crawl
Content-Type: application/json

{
  "url": "https://example.com/",
  "limit": 1
}

POST /browser-rendering/crawl
Content-Type: application/json

{
  "url": "https://example.com/",
  "limit": 1
}

2. Receive a successful response:

{
  "success": true,
  "result": "<uuid>"
}

{
  "success": true,
  "result": "<uuid>"
}

3. Poll the crawl status endpoint:

GET /browser-rendering/crawl/<uuid>

GET /browser-rendering/crawl/<uuid>

4. Receive an immediate failure response:

{
  "success": false,
  "errors": [
    {
      "code": 1001,
      "message": "Crawl job not found"
    }
  ]
}

{
  "success": false,
  "errors": [
    {
      "code": 1001,
      "message": "Crawl job not found"
    }
  ]
}

5. Continue polling every 2 seconds for 30+ seconds — response never changes.

---

Expected Behaviour

The GET request should return one of:
- A pending/in-progress status while the crawl is running
- The completed crawl results once finished

---

Cloudflare Browser Rendering Crawl not working

BUG: /browser-rendering/crawl endpoint returns "Crawl job not found"

Summary

Environment

Steps to Reproduce

Expected Behaviour

Cloudflare Browser Rendering Crawl not working

BUG: /browser-rendering/crawl endpoint returns "Crawl job not found"

Summary

Environment

Steps to Reproduce

Expected Behaviour

Similar Threads

Similar Threads

Similar Threads