Working with worker locally sometimes shows CF error page

I'm developing with Workers locally, but with the

--remote

--remote

flag so it runs on CF architecture. It generally works fine, but occasionally when I refresh I get this. Why is this, and is there reason to believe it will happen when my Worker is deployed live?

Erisa•12/8/23, 11:47 PM

When that happens there should be a corresponding error message in your terminal output

EErisa When that happens there should be a corresponding error message in your terminal...

MityaOP•12/9/23, 1:52 PM

It does, but I'm not sure why. It's the same URL, just the error happens when I hit refresh soon after the initial load (if I wait some seconds it's fine). Error is:

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.
✘ [ERROR] Uncaught (in response) Error: The script will never generate a response.

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.
✘ [ERROR] Uncaught (in response) Error: The script will never generate a response.

. Any thoughts on what this might be about?

Working with worker locally sometimes shows CF error page

Similar Threads

Similar Threads

Similar Threads