Is there a way to force workers to run in specific zones?
Is there a way to force workers to run in specific zones?
HA Worker will only run on zones it is bound to, if that is what you mean?
Cdo you mean zone as in cloudflare zone/website or zone as in some sort of geographical region
NYeah it is currently trying to find the closest to the user
NGeographical
CThere's smart placement: https://developers.cloudflare.com/workers/configuration/smart-placement/
If you need it for legal reasons or some very strict "only ever in x country/region" there's Enterprise's Data Localization suite stuff
If you need it for legal reasons or some very strict "only ever in x country/region" there's Enterprise's Data Localization suite stuff
Cloudflare Docs
Speed up your Worker application by automatically placing your workloads in an optimal location that minimizes latency.
NI know smart can place it closer to one of its region of other services like database but it doesn't do that for other APIs
NId prefer to min max the latency between the api and the worker rather than the latency between the worker and the user
Chmm what do you mean for "other APIs"? It does it with fetch requests from your worker
Smart Placement is enabled on a per-Worker basis. Once enabled, fetch requests (also known as subrequests) from your Worker are analyzed regularly. The Smart Placement algorithm determines the optimal placement to minimize the round-trip time (RTT) between the Worker and the back-end service the Worker is communicating with.https://developers.cloudflare.com/workers/configuration/smart-placement/
Smart Placement is only active for Workers that make more than one roundtrip to back-end infrastructure. If your Worker does less than one subrequest on average, Smart Placement will run the Worker at the data center closest to the user.
Smart Placement is a best-effort attempt. Smart Placement will not take action unless it is more performant than the default (which is running the Worker at the data center closest to the user).
Smart Placement only affects the execution of fetch event handlers. Workers without a fetch event handler will be ignored by Smart Placement. For Workers with both fetch and non-fetch event handlers, Smart Placement will only affect the execution of the fetch event handler.
NHow does it determine that it does have to move, here is says that it has to do a minimum of 1 subrequest but does it have to be the exact same?
NBut i believe i shouldnt worry since smart placement will figure out if it really is worth it or not
NThanks a bunch
Iguys
was there an outage for cron triggers for a few hours today from ~8:30am to ~3:30pm US Eastern Time?
i get stats sent to me every 30mins using workers cron triggers that i check whenever i find time in the day but the stats for ~8:30am to ~3:30pm seem to be simply missing.
was there an outage for cron triggers for a few hours today from ~8:30am to ~3:30pm US Eastern Time?
i get stats sent to me every 30mins using workers cron triggers that i check whenever i find time in the day but the stats for ~8:30am to ~3:30pm seem to be simply missing.
Cshould be same origin/per ip afaik, and yea it'll see if it's more performant to move or not
Cnothing in #cloudflare-status , I have ~8 or so crons running once a minute which seem fine but could be more specific. I would check your Workers Logs -> Cron Events to see if it ran or not
Iuh this is supposed to not be empty, right?
Cuhhh looks unrelatedly broken
Wugh
W
Wand event logs is the same
Wsigh
Cshould I escalate or you got it?
Wpls
Cwell that's raised but yea as far as I know/people have reported (and lots of us champs use cron events & notice stuff pretty quickly) cron events seem fine, maybe an issue with your worker?
Iwith just my worker?
i havent touched it in months tho
i havent touched it in months tho
CI assume it relies on some external components to work.
When cron events are fixed you'd be able to see if it executed or not, although errors details/logs
When cron events are fixed you'd be able to see if it executed or not, although errors details/logs
D
Cshould be fixed now, can look back at those cron events, should be able to look back that far I think if you've only got it once per 30 mins
Iall of them are success
however the stats were simply not sent to me for those few hours
very weird
ive been using workers for years and this is the first time this is happening
maybe im assuming this is workers fault
maybe my infra thats supposed to "receive" the stats were down
however the stats were simply not sent to me for those few hours
very weird
ive been using workers for years and this is the first time this is happening
maybe im assuming this is workers fault
maybe my infra thats supposed to "receive" the stats were down
CYou see cron events showing during that time as success?
Iyes
CSounds like the worker did indeed run then and it's something else during its run that went awry
Ishows no error tho
Ifor the last week
Iwhats wrong with this message
CDepends what the logic in your worker is doing, it looks like it does a few sub requests per run, if you don't check the response or have logic to not error on bad responses, then well that wouldn't show a worker exception
CCant use subtext with -#, too many people abuse
Ithats... weird
CLooks too close to bot "only you can see this" responses and too many people try to use it just to troll or impersonate bots, etc
Iif you don't check the response or have logici catch all possible "thrown" errors into error as value (Result<T,E>) in ts and deal with them explicitly (im coming from rust to ts but dont use rust for workers as wasm on workers is not there yet)
it should be type theory complete (though i doubt ts type checks are deep enough)
so its true that no error should be thrown in the workers environment
but all unrecoverable errors are supposed to be sent to me (which has happened till today)
however today no error logs were sent for potentially failed cron jobs
i guess thats because my local infra was down for some reason
anyway thanks for the help
JAnyone else's crons stopped triggering like 30 mins ago? Ours did and we didn't have any code changes 
AYup, my crons are not running since ~4 hours ago
AThere was https://www.cloudflarestatus.com/incidents/8qxgw783x9kv which was the dashboard not showing runs, but mine are literally not running as it's not producing output expected
ASun, 18 Aug 2024 12:20:28 - last time mine ran
JAh weird, ours stopped around 18 Aug 14:27 UTC
JWe just tried redeploying it and that seems to have caused it to get triggered a few times
ADeploying my worker now 
JAhh ok it seems like it's dead again
AYeah, mine aren't working even after a deploy, nothing on the status page either 
AI can't raise a proper ticket either as that's restricted to business 
W