13 days ago
Hi,
I went into weekend with all (but a few) my services perfectly working in my project across all environments.
My railway quota was being hit during weekend so my services stopped working, which is expected. I upped my quota and expected everything would be going back to working but my services are all showing
"No deploys for this service"
I am certain this can't be the expected behaviour as now I have to re-deploy every single service. I would like you to look into this and fix it for the future. Also: please adivse on how to set project AND environment based quotas; obviously, some projects are more important than others and same with environments (I need a different quota for staging than for prod).
Thanks and best regards
regarding selecting a related project:
ALL OF THEM ACROSS ALL ENVIRONMENTS (this is a true nightmare)
8 Replies
13 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
13 days ago
Next Bug:
I disconnected repos from my services to cleanly reconnect them because of the described issue above. Now, I want to reconnect the repo, it creates a new service, which is another nightmare because this would require me to rename everything and reconnect everything and set variables again everywhere.
Seriously, what is going on here!? This is so unnecessary.
I need to reconnect to the exact same services before also because of documentations and other people being dependent on it.
I would appreciate help asap as everything is fucked.
12 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 12 days ago
12 days ago
IIRC you can only set quota/limits by project. Additionally, as stated in the modal:
When your usage reaches this amount, we will shut down ALL your resources to prevent further charges.
So removing all deployments is intended behavior, as shutting down a service requires removing its deployments.
12 days ago
Also, reconnecting a Github repository does not create a new service. You must relink the repository through the service settings in the Source section.
12 days ago
1) I never agreed to making this public. Ask before you move on as this thread DOES include pseudonymised personal information which can be traced with ease to un-pseudonymised personal information, thus is against GDPR. See GDPR recital 26 and article 4.
2) shutting down all services is expected, but not removing all deployments in a way so your users have to add ALL of them again manually --> If you auto un-deploy, you have to auto re-deploy or offer atleast an option for that.
3) "reconnecting a Github repository does not create a new service" --> WRONG. It does create a new service more often than not next to the service you intent to reconnect because railway is quite buggy in this area.
4) FEATURE REQUEST: Railway really needs a environment based quota system -- in short: what's the purpose of modularity if you cannot play it on all levels.
Additionally: the mentioned option "quota by project" does not seem to exist. atleast I never stumbeled upon it since 2 years of using railway and I do not see it now. If someone could provide a link or screenshot about it I would be happy to learn about it.
12 days ago
Sorry I meant quota by workspace*
I have also just tested relinking a Github repository myself and it does not create a new service.
Also, there isn't a way to shutdown a service without removing its deployments. A service is kept active because there are active deployments.
0x5b62656e5d
Sorry I meant quota by workspace*I have also just tested relinking a Github repository myself and it does not create a new service.Also, there isn't a way to shutdown a service without removing its deployments. A service is kept active because there are active deployments.
12 days ago
about relinking Github:
again, this is a bug, thus you won't see this behaviour everytime.
about shutdown on quota hit:
again, this is not about removing its deployments but how it behaves after adding more coins.
11 days ago
@RAILWAY:
Any further information needed about the "Relinking the Repo leads to new service creation"-Bug? OR not interested?
The bug still happily persists across my projects -- even in projects i haven't touched in a while (ruling out a certain category of frontend state issues causing this).