I have a few builds that failed in Payload Cloud, but it looks like the UI is stuck and I'm not able to access the "settings" tab to destroy them.
Is there a way around this? Should I open a support ticket?
#Unable to destroy/retrigger failed builds on Payload Cloud
elder charm
calm mortar
@reef elbow let's look into this ASAP
ocean sphinx
This is the same issue I was referring to in #general . Thanks!
reef elbow
@ocean sphinx @elder charm could either of you give me the names of your project? I would like to see what state the project is in!
ocean sphinx
<@1095987858617151568> <@249649086968496128> could either of you give me the nam...
PAYLOAD-CMS-4A6FCD9
elder charm
I've got several in this state. I'll DM you my account details
forest ibex
I am experiencing this this morning (May 13) where build and deploy logs display however the "initial deployment in progress" bar has stalled at halfway for several hours. Deploy shows [18:48:31] INFO (payload): Payload Admin URL: /admin however the cms is not in fact deployed.
calm mortar
@forest ibex can you DM me with your project info? We will check into this immediately
forest ibex
<@511305637959827459> can you DM me with your project info? We will check into t...
Sent just now.
forest ibex
@calm mortar I think I know what's happening here but need to test to be sure. The initialization for the stalled projects was missing critical build scripts. Adding them after initialization does not appear to correct the issue. Will know more shortly.
forest ibex
@calm mortar I was correct (incorrect?) that the build scripts were wrong, and docker stuff missing. Oops. Nonetheless I now have a stray project which I cannot delete.
calm mortar
hey @forest ibex I am back in action here. I was in meetings all morning but will get on this immediately
forest ibex
@calm mortar I am 99% certain this project is DOA due to missing build scripts AND dockerfile … oops
Although build seems to be delayed/stopped on it's replacement: https://payloadcms.com/cloud/gravyboat/edit
That one, "edit" is about 4 commits out of date. When I try to manually trigger redeployment I get "failed toast"
wild bison
Hey @forest ibex I sent you a DM with some info, but I'll post here for others to see
The reason your deploy is failing appears to be because of a failed health check. Our system checks for a 200 response on the root / of the project.
Are you serving anything from the root? Can you check if that is the case for your project?
If not, you can add a simple redirect from / to /admin by putting this snippet in your server.ts
app.get('/', (_, res) => {
res.redirect('/admin');
});
It sounds like we need to surface these failed health checks to the user properly - as it is not evident that this is what is happening behind the scenes.
forest ibex
Awesome. I missed that. This is an adaptation of the preview example. Thank you for pointing this out! It would have taken me forever to find.
wild bison
We're discussing internally what is the best option for this moving forward to avoid this type of issue