workers-and-pages-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
🤖turnstile
radar
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
pipelines-beta
containers-beta
Deployment of static site failing
11:20:25.691 ✓ built in 6.17s 11:20:25.797 Success: Build command completed...
Deploying worker consumer is cutting off the existing long running connection from older version.
Worker is counting 1 fetch (with no redirects) as 2 subrequests
I know this because I wrote a test route that fetches until it throws the "too many subrequests" error, it stops at the 26th instead of the 51st. When I set the URL to get from another API, it can do 50 requests like normal, so it seems to be something about this specific API. My main question is: are there any cases other than redirects that would cause a Worker to count 1 fetch request as 2 subrequests?...
Hi Devs,

Compress a binary blob served as worker asset
wrangler dev is compressing the blob but not when it is deployed to the worker. How can I compress it? The attached screenshots show the difference when it is served on localhost vs production...
`wrangler types` breaks VS Code typing
pnpm wrangler types (Wrangler 4.40.1) and it added a new GlobalProps interface to my worker-configuration.d.ts. This appears to break types in VS Code - I now get Property 'Foo' does not exist on type 'Env' errors for all my bindings and environment variables (screenshot).
Manually editing worker-configuration.d.ts to remove the GlobalProps import makes the VS Code errors go away. How can I fix?...
CPU time limit ignored in paid worker

Accessing assets between different versions of the same worker
Preview deployment domain
Capacity temporarily exceeded & timed out
Started receiving messages about potential deadlock
A stalled HTTP response was canceled to prevent deadlock. This can happen when a Worker calls fetch() or cache.match() several times without reading the bodies of the returned Response objects. There is a limit on the number of concurrent HTTP requests that can be in-flight at one time. Normally, additional requests made beyond that limit are delayed until previous responses complete. However, because the Worker did not read the responses, they would never complete. Therefore, to prevent deadlock, the oldest response was canceled. To avoid this warning, make sure to either read the body of every HTTP Response or call response.body.cancel() to cancel a response that you don't plan to read from.Where are these coming from? I tried to narrow down to a logging statement in my code. But I think it's not coming from any of them. Nor can I figure out what would be triggering these. I tried to reproduce locally in my dev environment using the same parameters as the original call. But that wouldn't cause anything. Is there any way to find out where (in my code) these are coming from?...
How can I view the log from a failed deployment?
Preview deployments URLs
Pull request previews: Enabled(default)...TanStack Start with Deno runtime on Workers?
Infinite Pages delete error
OpenAI Completions compatibility for gpt-oss models?
/v1/chat/completions seems to implement Responses for gpt-oss, instead of Completions. Is this the intended behavior?
```sh
curl https://gateway.ai.cloudflare.com/v1/ACCOUNT_ID/GATEWAY_NAME/workers-ai/v1/chat/completions -H "Authorization: Bearer TOKEN" -X POST -d '{ "model": "@cf/openai/gpt-oss-120b", "messages": [ { "role": "user", "content": "hello" } ] }'
...deployed worker always returning 403 when uploading file via the routed domain.

worker deployment using wrangler fails [code: 10013]
An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]
A request to the Cloudflare API (/accounts/<account_ID>/workers/scripts/<worker_name>/routes) failed.
An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]
A request to the Cloudflare API (/accounts/<account_ID>/workers/scripts/<worker_name>/routes) failed.
Use ca/cert/key with Cloudflare Worker