Those kind of error pages usually appear if your browser is making a request that isn't valid accord
Those kind of error pages usually appear if your browser is making a request that isn't valid according to the HTTP specification.
When the schedule interval is more than 1 hour, a scheduled Worker may run for up to 15 minutes.. My job runs once per month.



text-to_Image (1) a few times i got the "upstream too busy", (2) is there any plan to add the resolution in the input request (3) what would be great value for num steps... i can try and guess but explanation would help foo.bar.com and a workers route for *.foo.bar.com/* that goes to my worker, plus a proxied DNS record for *.foo.bar.com. All that works fine. Then we decide to create a zone for bar.com and migrate off foo.bar.com into this zone. Added the same proxied DNS record to this bar.com zone and the same workers route. Issue we're seeing is that the requests seem to go straight to the origin server but they don't seem to be hitting the worker at all.foo.bar.com zone. I want the new bar.com to process these requests, not the old zone For now, this is only available for Workers that are deployed to a “root” hostname like “example.com” and not specific paths like “example.com/path/to/something.” We plan to introduce more optimizations in the future that can preload specific paths.Edit: If it's more then ~50ms then it sounds more like global scope then cold start not working though, tcp connect isn't that long
#[event(fetch)]
async fn main(mut req: Request, _env: Env, _ctx: Context) -> Result<Response> {
if req.method() == Method::Post{
if let Ok(body) = req.text().await{
match serde_json::from_str::<TVSignal>(&body) {
Ok(tvs)=> {
match Fetch::Request(tvs.request()).send().await {
Ok(_) => Response::ok("Success"),
Err(_) => Response::error("Error to send request to OKX", 502),
}
},
Err(_) => Response::error("Can't deserialize json to pass value", 400),
}
}else {
Response::error("Need text body",400)
}
}else {
Response::error("There are apis, please request with POST",400)
}
}✘ [ERROR] Error while creating remote dev session: TypeError: fetch failed
at fetch
{
cause: Error: connect ETIMEDOUT 2606:4700:3031::ac43:cb34:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
errno: -60,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '2606:4700:3031::ac43:cb34',
port: 443
}
}