Browser Rendering worker re-executes before timing out

👋 I'm running browser rendering to scrape pdfs. Running wrangler dev locally ($ npm run dev -- --remote -e stage --test-scheduled) and triggering scheduled event with $ curl "http://localhost:8787/__scheduled", once the worker execution time hits around 80 seconds, it starts executing all over again as if the curl was called again - but it wasn't called again. Is this by design in workers? cc: @Walshy
2 Replies
Walshy
Walshy•2mo ago
That sounds like a bug i'd recommend filing a report in https://github.com/cloudflare/workers-sdk/issues with a repro
Honumael (MasterQuestMaster)
I also have a problem where my worker executes twice. For me it runs again immediately after the first run is done (which takes a few seconds). Did you manage to solve this yet? Edit: It seems for me it was because of the browser favicon. Since you load through curl, it's unlikely that we have the same issue.
Want results from more Discord servers?
Add your server