claudiobizzotto / delete-linkedin-activity

Absolutely hacky, yet effective, way of automating Linkedin activity deletion.
51 stars 18 forks source link

I keep getting the "Uncaught (in promise) Error: async call timeout limit reached" error #5

Open mig281 opened 2 years ago

mig281 commented 2 years ago

This happens after every 10-11 posts is there any way to increase or change this limit?

Uncaught (in promise) Error: Async call timeout limit reached
    timeoutHandle debugger eval code:18
    setTimeout handler*timeout/< debugger eval code:17
    timeout debugger eval code:16
    awaitThisTimed debugger eval code:52
    init debugger eval code:91
    init debugger eval code:120
    async* debugger eval code:125
[debugger eval code:18:26](chrome://devtools/content/webconsole/debugger%20eval%20code)
    init debugger eval code:123
    AsyncFunctionThrow self-hosted:699
    (Async: async)
    init debugger eval code:120
    InterpretGeneratorResume self-hosted:1485
    AsyncFunctionNext self-hosted:695
    (Async: async)
    <anonymous> debugger eval code:125
    getEvalResult resource://devtools/server/actors/webconsole/eval-with-debugger.js:243
    evalWithDebugger resource://devtools/server/actors/webconsole/eval-with-debugger.js:167
    evaluateJS resource://devtools/server/actors/webconsole.js:1127
    evaluateJSAsync resource://devtools/server/actors/webconsole.js:1019
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
noverotajs commented 2 years ago

all timeouts change from 1000 to 5000 and all works good :)

quantuminformation commented 1 year ago

times out Uncaught (in promise) Error: Async call timeout limit reached

charona commented 1 year ago

Not working for me in either Firefox or Brave in 2023. Script keeps running, but no Likes are deleted. Didi anybody ever update this to work in 2023? Probably just takes some small tweaks :)

claudiobizzotto commented 1 year ago

delete-posts.js has been updated recently (#6). Can you please try again and see if post deletion works for you now?

jason-eu commented 1 year ago

I got it as well, a browser restart fixed it for me.

dirkduplooy commented 8 months ago

Hi there the process starts with Delete repost and then nothing happens. These are the logs in Chrome

** Starting activity deletion *** VM289:142 >>> Deleting loaded activity VM289:151 Menu found (id:ember108) Promise {} VM289:159 delete button in menu found 9xyc0sf0m29oh2hkx533g5ch0:5615

   POST https://www.linkedin.com/v2NPUJd0 400 (Bad Request)

(anonymous) @ 9xyc0sf0m29oh2hkx533g5ch0:5615 o @ 9xyc0sf0m29oh2hkx533g5ch0:5615 (anonymous) @ 9xyc0sf0m29oh2hkx533g5ch0:5662 value @ 9xyc0sf0m29oh2hkx533g5ch0:5663 value @ 9xyc0sf0m29oh2hkx533g5ch0:5662 beacon @ 9xyc0sf0m29oh2hkx533g5ch0:5732 value @ 9xyc0sf0m29oh2hkx533g5ch0:5736 value @ 9xyc0sf0m29oh2hkx533g5ch0:5736 value @ 9xyc0sf0m29oh2hkx533g5ch0:5820 value @ 9xyc0sf0m29oh2hkx533g5ch0:5791 (anonymous) @ 9xyc0sf0m29oh2hkx533g5ch0:5807 requestIdleCallback (async) value @ 9xyc0sf0m29oh2hkx533g5ch0:5807 value @ 9xyc0sf0m29oh2hkx533g5ch0:5808 (anonymous) @ 9xyc0sf0m29oh2hkx533g5ch0:5809 setTimeout (async) value @ 9xyc0sf0m29oh2hkx533g5ch0:5809 value @ 9xyc0sf0m29oh2hkx533g5ch0:5789 value @ 9xyc0sf0m29oh2hkx533g5ch0:5854 fireEnvelope @ d5cpletq0e0xbqklhdhollt5e:18895 value @ 9xyc0sf0m29oh2hkx533g5ch0:5855 value @ 9xyc0sf0m29oh2hkx533g5ch0:5854 firePVE @ d5cpletq0e0xbqklhdhollt5e:18893 firePageViewEvent @ d5cpletq0e0xbqklhdhollt5e:19429 handleTracking @ d5cpletq0e0xbqklhdhollt5e:25589 installModifier @ d5cpletq0e0xbqklhdhollt5e:7694 (anonymous) @ bpj7j23zixfggs7vvsaeync9j:3794 e.untrack @ bpj7j23zixfggs7vvsaeync9j:5852 install @ bpj7j23zixfggs7vvsaeync9j:3794 (anonymous) @ bpj7j23zixfggs7vvsaeync9j:5319 e.track @ bpj7j23zixfggs7vvsaeync9j:5843 commit @ bpj7j23zixfggs7vvsaeync9j:5319 commit @ bpj7j23zixfggs7vvsaeync9j:5333 Nt @ bpj7j23zixfggs7vvsaeync9j:5339 _renderRoots @ bpj7j23zixfggs7vvsaeync9j:834 _renderRootsTransaction @ bpj7j23zixfggs7vvsaeync9j:839 _revalidate @ bpj7j23zixfggs7vvsaeync9j:845 invokeWithOnError @ bpj7j23zixfggs7vvsaeync9j:6108 flush @ bpj7j23zixfggs7vvsaeync9j:6092 flush @ bpj7j23zixfggs7vvsaeync9j:6120 _end @ bpj7j23zixfggs7vvsaeync9j:6221 end @ bpj7j23zixfggs7vvsaeync9j:6169 _run @ bpj7j23zixfggs7vvsaeync9j:6228 _join @ bpj7j23zixfggs7vvsaeync9j:6226 join @ bpj7j23zixfggs7vvsaeync9j:6181 l @ bpj7j23zixfggs7vvsaeync9j:3451 (anonymous) @ bpj7j23zixfggs7vvsaeync9j:1765 e.flaggedInstrument @ bpj7j23zixfggs7vvsaeync9j:2345 handleEvent @ bpj7j23zixfggs7vvsaeync9j:1765 handleEvent @ bpj7j23zixfggs7vvsaeync9j:1629 n @ bpj7j23zixfggs7vvsaeync9j:1659 o._eventHandlers. @ bpj7j23zixfggs7vvsaeync9j:1666 init @ VM289:162 await in init (async) (anonymous) @ VM289:192 VM286:186 Error: Async call timeout limit reached init @ VM286:186 await in init (async) (anonymous) @ VM286:192 VM289:186 Error: Async call timeout limit reached

ibnunowshad commented 1 month ago

I got it as well, a browser restart fixed it for me.

May, please add more detail? Does that mean new browser?