though you might benefit from smart placement if you're not already using that:
L
TT
MM
O
WOOWOW
T
OO
R would anyone have a clue as to why a worker with a scheduled event that uses fetch() gets an error in the network code. but if i hit my worker via http, i can then make that remote API call just fine. both 
scheduled and fetchgetIncidents, which makes a fetch call to the API. exact same code works in one way, not the other
A
DDWDW
Bcurl -i https://api-dev.hhc.workers.dev/ --header 'Content-Length: 0'workers.dev domain only, not custom domainContent-Length: 0 header setB
A/
MM<title>Worker threw exception | bfstats.ragnarok.workers.dev | Cloudflare </title> HTML page back. Hitting my custom domain works as usual thoughM
MMT
M
M
AM
T
MMT (for legal reasons, this is a joke)TMM
J
Cache-Control: public, max-age=0, must-revalidate.
M
L
scheduledgetIncidentscurl -i https://api-dev.hhc.workers.dev/ --header 'Content-Length: 0'workers.devContent-Length: 0<title>Worker threw exception | bfstats.ragnarok.workers.dev | Cloudflare </title>Cache-Control: public, max-age=0, must-revalidate