Abort signal is not triggered

When I use this code, it doesn't trigger when user disconnects from the worker.

But it shows an error

X [ERROR] Uncaught (in promise) Error: Network connection lost.

X [ERROR] Uncaught (in promise) Error: Network connection lost.

X [ERROR] Uncaught (in promise) Error: Network connection lost.

X [ERROR] Uncaught (in promise) Error: Network connection lost. in the console somehow.

request.signal.addEventListener('abort', () => {
   console.log(123)
});

request.signal.addEventListener('abort', () => {
   console.log(123)
});

request.signal.addEventListener('abort', () => {
   console.log(123)
});

request.signal.addEventListener('abort', () => {
   console.log(123)
});

What's the problem?

AgentCordOP•9/2/24, 5:57 PM

Is there any other way to detect if user disconnects?

James•9/2/24, 5:58 PM

AFAIK, this isn't really possible with Workers, unless you're doing WebSockets or something similar.

AgentCordOP•9/2/24, 5:59 PM

Oh...... Okay

AAgentCord Oh...... Okay

Hello, I’m Allie!•9/2/24, 6:39 PM

I'm wondering, if you race a Promise that resolves in a certain amount of time against a Promise that resolves when aborted, then pass it into a waitUntilwaitUntil, it might work?

HHello, I’m Allie!I'm wondering, if you race a Promise that resolves in a certain amount of time a...

AgentCordOP•9/2/24, 7:14 PM

Already using waitUntil()waitUntil() to check the state after some delay and the abort callback doesn't get called anyway

hfcRed•9/4/24, 8:02 AM

From my own experience workers will continue running until they finish the request, even when the client aborts

hfcRed•9/4/24, 8:03 AM

Not sure if this is true, but thats the behavior I'm getting

Abort signal is not triggered

Similar Threads

Similar Threads

Similar Threads