Hey there! We've found the following might help you get unblocked faster:

• 🧵 Deployment stuck after successful build (us-east4)

• 🧵 Docker image push is extremely slow

• 🧵 Postgres

If you find the answer from one of these, please let us know by solving the thread!

There are no solutions in these posts other than retry later.

Even after several retry, the service still stuck in "complete" status, and the public URL returns a 502 HTTP error. I have other 2 services with the same application code, one for the cron scheduler, and another for the workers, and they are correctly Online.

In Build Logs, the "image push" task still running indefinitely (see the image attached in the first message of this thread).

Could I get a link to the service thats stuck? All appear online at an initial glance.

https://railway.com/project/c95227aa-7de5-4c02-aa47-5c9bfca803bf/service/efa702aa-63f8-4ff4-9b04-4695a79c4dc8/settings?environmentId=b16e84dd-d023-4eaa-94c5-bd36cfa303b9

And also this

https://railway.com/project/31c1e71c-57e7-4ac5-9378-7ad6bf344e89/service/177a986b-a577-4527-b00f-2d9c043dbcad?environmentId=ffe33cd9-b0cd-43a7-bcbc-e0315557aaa4

They are two app services in two different projects, same status, same 502 error

The image push finished, and your app started without issue. It's just a rounding error for the progress and us not switching from a spinner to a check, purely a UI quirk.

Completed means your app has exited. It wouldn't be a problem with our platform or product, so I have opened this thread up to the community so they can help you debug why your application may be exiting.

Yeah as brody said, I've only ever seen the completed status when a job exits with a exit code of 0 (success). Basically means that your services process just finished running and closed.

I'm not familiar with laravel so can't help too much there but are you able to start the apps in production mode with the same configuration on localhost?

Seems like the app is building and then the deploy step exits immediately. I would start by checking if your start command matches what you would expect

I found the problem following the documentation for Laravel deployment (https://docs.railway.com/guides/laravel). The initial script after every deployment must run as pre-deploy command for the http service and as start command for cron and queue worker services. I had configured the script as start command for all. Moving the script from start command to pre-deploy command in app service solved the problem.