Lthanks! Btw, why does the
https://developers.cloudflare.com/workers/runtime-apis/handlers/scheduled/#syntax
scheduled example even use waitUntil instead of just blocking until the task has finished?https://developers.cloudflare.com/workers/runtime-apis/handlers/scheduled/#syntax
LIf my
scheduled handler takes longer than 30s, is the solution to NOT use waitUntil? Or what is the solution? :)Lso if I don't use
waitUntil, as soon as scheduled returns it will cancel all promises spawned by scheduled?Lok, and how can I spawn many promises and join all of them using something like a join set?
LI have to do many fetch requests and insert data into my D1 db. and I want to parallelize them
Lthanks. btw, why use
waitUntil instead of awaitwould it also work to call
waitUntil for each of the many promises that I want to run?Lso I have to use a semaphore? or what's the recommended solution to limit the requests?
Lthanks!
Lwhat kind of queue?
Ldo you mean a worker that acts as a queue handler?
Lcan it be the same worker that has the
scheduled handler?Lso I'd split the tasks into batches of 6?
Lok thx. btw, where is this written? :)
Lhttps://developers.cloudflare.com/workers/platform/limits/#how-many-subrequests-can-i-make
The 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?Lah, also 50
Lso if I split it into batches of 6 and trigger a
queue 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?)Lhm, I can't enable queues on the free plan :/
A 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?
(So it would only drag out the wall time.)
LI basically need to make 60*2 requests every 12 hours to update data in my db
Land I'd like to stay on the free plan for now
Lso if I spawn 7 fetch requests, the 7th will be delayed and automatically run as soon as one of the first 6 completes?
Lah great :)
Lthen I still have the issue that the total number of requests per worker request is 50
Lcan I pass custom args to each
scheduled invocation?Le.g. trigger it twice, with a bool flag to process the first or second half
Lis it possible to pass contextual args to the
scheduled handler?La hacky way is to check the value of
event.cron..Lyeah, seems like a good enough way :)
Lbtw, where did you find this in the docs? :)
Lah thanks!
FHey, is the Workers File API available yet? I want to do something like this https://stackoverflow.com/a/65672740/12037631
Stack Overflow
These recent days I tryed multiple times to upload file to file.io using cfworkers but it returns error this is my source code:
async function handleRequest() {
const file = fetch('https://upload.
async function handleRequest() {
const file = fetch('https://upload.
FThanks! I will try this
FThe Workers runtime is designed to be JavaScript standards compliant and web-interoperable. Wherever possible, it uses web platform APIs, so that code …
KMost of the globals/APIs you get from browsers aren't documented but are just available
FOh cool, I came here to ask about the Files API because I couldn't find it on that page
RI have an usecase to cover. After every 1000 worker invocation I need to hit an api to external system. how can i do that? Any idea on this? Workers will as usual get data from user, the data will be stored on lets say d1. And after 1000 data I get from user, I need to push that data to external system. Any idea here?
GWow, debugging a CF Worker (typescript) in WebStorm for the first time is pretty powerful! 
https://blog.cloudflare.com/debugging-cloudflare-workers
https://blog.cloudflare.com/debugging-cloudflare-workers
The Cloudflare Blog
We provide many tools to help you debug Cloudflare Workers; from your local environment all the way into production. In this post, we highlight some of the tools we currently offer, and do a deep dive into one specific area - breakpoint debugging - a tool we recently added into our workerd runtime.
ⱤHow to cache range request in cloudflare worker?
Scoming from Notepad, that's crazy
Ɽ
CI believe the cache API respects the range header so should match the headers on
match.
DWhat happens if I use the cache-control request header and
cacheEverything: true?
UYeah all cache everything does is allow caching all requests regardless of the extension. It will use the cache headers unless you specifically tell it to use a certain ttl
MHello, when I selected ssl encryption mode as Flexible, it gives unknown web server error (520 error).
with Full mode, it works well, please let me know what is wrong
with Full mode, it works well, please let me know what is wrong
Myou recommend to use Full at least? with even free ssl
MI have only free ssl, so I am going to use flexible mode, Full with letsencrypt ssl is better than Flexible?
Mgot it, thank you
SHello folks, I'm using
resolveOverride from RequestInitCfProperties (https://developers.cloudflare.com/workers/runtime-apis/request/#requestinitcfproperties) so that I can proxy the request to specific domains. However it seems like this only works when deploying the workers, and doesn't seem to work with npx wrangler dev. Is there a way to make it work?