Error deploying pages project to preview environment
Using wrangler 3.15.0, I cannot deploy my pages project to a preview environment. Using the following pages deployment command:
![No description](https://cdn.answeroverflow.com/1170806312733528084/Screen_Shot_2023-11-05_at_1.22.37_PM.png)
33 Replies
It sounds like you're running into https://github.com/cloudflare/workers-sdk/issues/3966, where your Functions are erroring after being uploaded
so maybe a compilation error in the fuctions could be causing this?
not a compilation error, something at runtime specifically
is there a log i could look at myself?
unfortunately there is not. If you post a deployment ID, I can ping someone tomorrow to take a look for you
from the url looks like this could be the deployment id:
looking forward to understanding more tomorrow
9604495b-8d76-4a37-890a-4131f5a6103e
ok ![ty](https://cdn.discordapp.com/emojis/814897220489969674.gif)
thanks, I'll ping someone to pull logs for you, sorry for the trouble
Out of interest, does it work locally with
pages dev
? That might be a way you can shortcut figuring this out if it errors there tooyeah sure does
that's no fun, sorry. Hopefully the logs will yield more info
well, getting an issue with 3.15.0 that im not getting with 3.4.0
there any issues w/ d1 bindings that could be causing this? (ive tried to deploy with 3.4.0 as well)
not to my knowledge đ¤ you might try asking in #d1-beta
some logs were pulled for you @landon :
could not resolve binding "BUILD_SCHEDULER"
something about your service binding config is incorrect
double check your environments and everything there is setup correctlyWill do thank you!
i checked to make sure its bound through the UI. i selected "production" but its linking to a staging version (our worker is confusingly named
https://dash.cloudflare.com/e7526284f9ee484875c61723e78af4ae/workers/services/view/build-scheduler-staging/staging i get a 404 from that link, but f i replace that last path parameter of "staging" with "production" it resolves
build-scheduler-staging
)https://dash.cloudflare.com/e7526284f9ee484875c61723e78af4ae/workers/services/view/build-scheduler-staging/staging i get a 404 from that link, but f i replace that last path parameter of "staging" with "production" it resolves
hmmm, is
build-scheduler-staging
a very old worker that uses service environments or something like that? What's your account ID?
dumb question, it's in your url above e7526284f9ee484875c61723e78af4ae
đ
what happens if you try and edit the binding and point it to the production
env? (service environments were an old thing that's since legacy, so every worker has a production
env that's just default nowadays)I tried that it had no effect
The link still pointed to staging
Can you check the payload being sent from the dash when you make that change, in your browser's network reqs?