C
C
P
MM
XCXCCX
LworkUntil will keep the Worker alive for 30 seconds.Is that true? Where is this documented? I don't see a limit written here https://developers.cloudflare.com/workers/runtime-apis/handlers/fetch/#contextwaituntil
L
scheduled cron worker needs to run for more than 30 seconds?L
scheduled example even use waitUntilscheduled handler takes longer than 30s, is the solution to NOT use waitUntilwaitUntilscheduled returns it will cancel all promises spawned by scheduled?LLLwaitUntilawaitwaitUntilscheduled handler?LLLThe limit for subrequests a Worker can make is 50 per request on the Bundled usage model or 1,000 per request on the Unbound usage model. Each subrequest in a redirect chain counts against this limit.So this is a limit for the total number of requests I can make when
scheduled is triggered. What's the limit on the free plan?LLqueue event for each batch, each queue handler invocation could theoretically make 50 requests? (in other words, that's a way to get around this limit?)LA Workers subscription is required to enable Queues.
LIf you have one big array of items, I would maybe run a batch of 6 promises at a time, but that would drag out on the time allocation.But workers are charged based on cpu time, not wall time, even when triggered by a cron schedule, right?
LLLLLLscheduled invocation?LLscheduled handler?Levent.cron..LLL
F
FF
K
scheduledscheduledscheduledscheduledscheduledscheduledscheduledscheduledscheduledqueueevent.cron