# Step to install Bun using the official oven-sh GitHub Action
- name: Setup Bun
uses: oven-sh/setup-bun@v2
with:
bun-version: latest # You can use "latest" or a specific version
E
I
D
D
B
pages_build_output_dirmain
AA
A
C
TC
R
so trying here. I've got a worker that uses a schedule. locally, it runs just fine. but in production, something weird happens. when it tries to use http to hit an API, it gets a 521 response. now here's the weird thing. i added a fetch() to the code so i could run my worker via the browser. the same network call there works, so its literally just failing when cloudflare executes it on a schedule. it's a bit messy now, but the code is here -https://github.com/cfjedimaster/cloudflareworkers-demos/blob/main/getincidents/src/index.js any ideas?
F
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.RT
D
colocity refers to the city where the request was made from?
A
CCC
AAD
✘ [ERROR] Wrangler cannot validate that your Worker name matches what is expected by the build system. Please retry the build.
KKKA
L
TLT
though you might benefit from smart placement if you're not already using that:L
TT
MM
O
WOOWOWT
OOR 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 otherAcity✘ [ERROR] Wrangler cannot validate that your Worker name matches what is expected by the build system. Please retry the build. const response = await env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
prompt: "What is the origin of the phrase Hello, World",
});scheduledgetIncidents