Sorry for the trouble. During the recent Railway Platform Outage, which has since been resolved, we reset GitHub credentials as a precaution. Since then, new pushes can stop triggering deploys until the GitHub integration is disconnected and reconnected. Redeploying an older deployment from before the incident won't fix this and can fail.

To fix it, disconnect and reconnect GitHub on your Railway account, check that the Railway GitHub App still has access to the waqas20/unilinkapi repo, then push a new commit or deploy the latest commit for the service.

I'm experiencing the same issue, but I've already tried all three suggested steps.

I've disconnected and reconnected GitHub, verified the Railway GitHub App permissions, and pushed a new commit.

I also tried deploying manually using railway redeploy --from-source, but the CLI immediately returns:

"Deploys have been paused temporarily"

My project still shows "Limited Access", despite having an active Trial account with remaining credits.

Could this be an account-level restriction that hasn't been lifted after the security incident?

Just tried these steps as well it still does not work even redeploying does not push the altest commits to raileway

Our incident response reset every Railway GitHub App installation, which is the usual cause of this. In GitHub, open Settings, then Applications, then Installed GitHub Apps, and make sure Railway is installed with access to this repository, reinstalling it if it's missing. Then disconnect and reconnect the repository in the service's settings in Railway and run Deploy Latest Commit. If it still doesn't work after that, reply here. We've also passed this to our engineering team.