Errors / checked October 9, 2026
Error 1101: Worker threw exception
The error
The error page a visitor gets when a Cloudflare Worker throws an unhandled JavaScript exception, with a Ray ID. Cloudflare's support docs title it "Error 1101: Rendering error". In Workers metrics the invocation status is Worker threw exception (scriptThrewException); a scheduled Worker started by a Cron Trigger has no visitor, so its exceptions only show in Cron Events and Workers Logs.
Quick fix
- Find the exception: run wrangler tail and read the exceptions field, or filter Workers Logs with $metadata.error EXISTS. For a Cron Trigger, Settings > Trigger Events > View events lists the last 100 runs.
- Fix the code that throws (an undefined variable or binding, a type error, a rejected Promise you never caught, a failed fetch you treated as a success), then redeploy and keep tailing to confirm.
- If the message says "The script will never generate a response", a Promise the response depends on never settles, or a WebSocket is never closed. Resolve or reject every such Promise.
Why this happens
Cloudflare returns 1101 when a Worker throws a JavaScript exception that nothing catches, so the request ends without a response. It is your code, not a Cloudflare outage; an outage shows other 11xx codes and appears on the status page.
Other solutions
- Enable source maps so the stack trace points at your original files and lines.
- Wrap a scheduled handler's work in try/catch and log the error with enough context to rerun the job by hand.
- If the scheduled job only calls a URL, an outside scheduler can call it on your cron schedule instead and keep the result. RunLater retries a failed call up to 10 times with exponential backoff, keeps each response 7 to 90 days by plan, and emails you when a run fails after its retries.
Check a schedule before you deploy it: the cron expression explainer shows the next 10 run times.
Frequently asked questions
Is Error 1101 a Cloudflare outage?
No. 1101 means your Worker threw an exception. Cloudflare documents other 11xx codes as problems with the Workers runtime itself, and those show on cloudflarestatus.com.
What is the difference between 1101 and 1102?
1101 is an unhandled exception in your code. 1102 means the Worker went over its CPU time or another resource limit.
Where do I see exceptions from a Cron Trigger?
In the Worker's Cron Events (the 100 most recent scheduled runs) and in Workers Logs, which keeps them longer and can filter by outcome. wrangler tail shows them live.
Have the URL called on schedule, with retries
RunLater calls your URL on a cron schedule or at an exact time, in your timezone, retries failed calls with backoff and logs each response, so a timeout or a 5xx shows up in a log instead of disappearing.