All Cloudflare Workers Returning Error 1101 With No Logs Since Early February 2026

What this error means

Error 1101 — Worker threw exception; custom domains also fail; Workers Logs tab completely empty even in real-time; service completely unusable is a Cloudflare failure pattern reported for developers trying to fix cloudflare workers suddenly returning error 1101 across all projects with zero logs available — cannot diagnose which worker or line caused the runtime exception because logging is broken too.. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Cloudflare Community thread reports total outage affecting all Workers projects with no diagnostic path since Error 1101 silences all invocation logs. Real-time logs completely empty. Custom domains bound to Workers also fail. Production deployment blocker for any business using Cloudflare Workers.

Common causes

• Cloudflare Community thread reports total outage affecting all Workers projects with no diagnostic path since Error 1101 silences all invocation logs. Real-time logs completely empty. Custom domains bound to Workers also fail. Production deployment blocker for any business using Cloudflare Workers.

Quick fixes

1. Confirm the exact error signature matches Error 1101 — Worker threw exception; custom domains also fail; Workers Logs tab completely empty even in real-time; service completely unusable.
2. Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://community.cloudflare.com/t/all-workers-returning-error-1101-with-no-logs-since-early-february-2026/891401

Evidence note: Cloudflare Community thread reports total outage affecting all Workers projects with no diagnostic path since Error 1101 silences all invocation logs. Real-time logs completely empty. Custom domains bound to Workers also fail. Production deployment blocker for any business using Cloudflare Workers.

Related errors

• Cloudflare

FAQ

What should I check first?

Start with the exact Error 1101 — Worker threw exception; custom domains also fail; Workers Logs tab completely empty even in real-time; service completely unusable text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Cloudflare workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Error 1101 — Worker threw exception; custom domains also fail; Workers Logs tab completely empty even in real-time; service completely unusable.