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
The deployment ran on Cloudflare-hosted Workers Builds with npx wrangler preview.
Describe the Bug
When Workers Builds automatically deletes a Worker Preview after a Git branch is removed, its deployment-specific workers.dev URL can keep returning HTTP 500 with Cloudflare Error 1101. The branch-named Preview URL returns 404.
Steps to reproduce
Connect a Worker to a GitHub repository through Workers Builds. Enable isolated Worker Previews and automatic Preview deletion on branch removal.
Push a non-production branch and wait for its automatic Preview deployment. Save both the branch-named URL and the deployment-specific URL. Verify the same working GET route on both URLs returns 200.
Delete the Git branch. Verify that the Preview disappears from the dashboard and the branch-named URL returns 404.
Request the same GET route on the deployment-specific URL with a fresh query parameter and Cache-Control: no-cache.
Expected behavior
After Preview cleanup completes, the deployment-specific URL should return a not-found response.
Actual behavior
The deployment-specific URL for 688c941b still returned 500 / 1101 more than 11 hours after branch deletion, including a check on 2026-11-18 at 10:37 UTC. The branch-named URL returned 404, and the production endpoint returned 200.
Related to cloudflare/workers-sdk#16170. The HTTP 500 here is reproducible on the deployment-specific URL after automatic deletion.
Please provide any relevant error logs
Workers Builds Preview lookup returned HTTP 404 with code 12043.
Workers Preview deployment lookup returned HTTP 404 with code 10025.
Lookup of the exact Worker version returned HTTP 404 with code 10071.
HTTP events showed edgeResponseStatus=500 and originResponseStatus=0 for the failing request. Successful invocations for the version were recorded before deletion. The post-deletion query returned no invocations for that version.
Could you check where Error 1101 is generated and whether automatic deletion left a routing or dispatch entry for 688c941b? If a stale entry exists, please remove it and confirm the expected behavior of the retired URL.
Activity