One service is not deploying with new GitHub merges
I have a Railway app with two services (both discord bots) from the same monorepo. Earlier today both services (bots) redeployed fine when there was a merges to the configured GitHub branch. Just now I merged other changes and one bot did not redeploy as expected while the second one redeployed as expected.
The bot that not redeploy did have codes changes inside of its watched directory, but just failed to do anything. Both bots are from the same monorepo, and from the same GitHub repo.
Is there anyway to force the service to redeploy using the new merged code?
9 Replies
Project ID:
5699151a-d2d8-47c5-9c29-35462dd2497f5699151a-d2d8-47c5-9c29-35462dd2497f
absolutely no indications on the UI of a an attempt to deploy it?
the team may want to look into this, so I'll ask ahead of time, can you send the service id for the service that is not deploying?
Actually, this might be on my end. Sorry, might have jumped the gun. Give me a couple of minutes to confirm. I think I mixed up something in the config.
no worries
Yup, my bad. Sorry about that. This definitely working now that I fixed my mistake.
mind sharing what was missconfigured?
We changed some stuff in the repo on merging, etc and merged into the wrong branch. I forgot about that over the holidays.
ah yep that would do it