Deploy failed after forking environment
After forking my main environment for a temporary test environment and changing some settings I cannot deploy.
Project ID: db439bde-0aa2-416f-aaa5-2c3e9deefc2f
26 Replies
Project ID:
db439bde-0aa2-416f-aaa5-2c3e9deefc2fQuick follow up here. We don't have any error logs available to start looking for the actual issue.
you two are on the same team?
Sort of, I'm more of a business development guy
I also do a little frontend here and there
is scot an admin on the team?
Yeah I am. I'm the backend dev and manage deployment
gotcha, but are you set to an admin on the team?
Yep, although my GitHub account is not linked to the email address I'm using on railway just yet.
could you go ahead and do that?
Done
still getting these errors?
Yes
Tried it again just now with the same result
what kind of change are you trying to deploy?
It's a fork of our development environment. I only changed a couple of branches (to test the new branch before creating the PR and merging) to test everything out. And I added one extra service
can you deploy changes on other projects in the same workspace?
On different environments on railway?
If so yes, our development branch is still working and can make changes there
in a different project
would you happen to be on safari?
Chrome
can you show the error you get back from the api and the console errors if applicable
The only error I get is the screenshot posted above
I checked the network calls going to the railway server as well but I can only see that exact error message in there
gotcha, thanks for checking
will flag the team now!
Thanks!
just needed to get some preliminary questions out of the way is all
Thread has been flagged to Railway team by @Brody.
Hi @scot5,
It is failing to deploy because one of the services was deleted. We will create a fix for this, but in the meantime you discard the changes from the "<deleted service>" from here
Unclear how that happened. Looks like that was the one service I added to the project. Regardless, the discard button does nothing for me. Removing all settings and variables does not fix the solution either
I will fork a new environment. Try again and deploy the new service after deploying all other services
(the discard button does work on all other services, only the deleted service cannot be discarded)