When your workspace compute hard limit is reached, all services are taken offline and new deployments, including those triggered by GitHub pushes, are blocked. You can raise or remove the hard limit at your workspace usage page by clicking "Update limits." Once the limit is above your current cycle spend, services will automatically redeploy (provided the stoppage was within the last 30 days). Could you share more detail on what you mean by "Vercel integration" so we can help with that part as well?

costs are fine and under limits. can you read previous threads? i had the same issue exactly in the past

Your workspace is active on Pro with no billing issues and your usage is within limits, so the hard limit isn't the cause here. We can see a previous thread from April where GitHub integration stopped working, which was resolved. Could you share what specifically is not working right now - are GitHub pushes not triggering new deployments, or are you seeing an error? Also, could you clarify what you mean by "Vercel integration" so we can help with that part?

nothing triggers a new deployment

Your services show successful deployments across most environments as recently as June 29, so the GitHub connection has been working. Could you share the specific environment and branch where pushes are no longer triggering deployments, along with a commit SHA and its UTC timestamp that should have triggered a deployment but didn't?

29 was manual deployment i think.

here is a pr that wont start railway

https://github.com/optimal-platform/Optimal/pull/672

this is about preview envs only

We can confirm that PR #672 did not create a PR environment, and the last auto-triggered PR environment we see is from early June. This matches the pattern from your April thread where the GitHub integration stopped responding. Could you check that the Railway GitHub App still has access to the Optimal repo and has no pending permission requests? If everything looks correct on the GitHub side, try disconnecting and reconnecting the repo in your service settings.

uninstalled railway from github, disconnected from railway - then connected again, nothing changes - even after reopening a pr

Since reinstalling the GitHub App and reconnecting the repo hasn't restored PR environments, and this matches the same pattern from your April thread, the standard self-serve steps are exhausted. Could you confirm that PR environments are still toggled on under Project Settings > Environments? Also, is PR #672 opened by a GitHub user who is a member of your Railway workspace or invited to your project? PRs from users outside the workspace won't trigger environments.

pr env eabled, prs opened by me

does my main test env (the parent of pr envs) need to be connected to a branch for PR envs to work?

any updates?