15 days ago
I’ve already tried everything on my end. I updated 4 variables, and immediately after that Railway started getting stuck nonstop. I also deleted a few variables to test if they were causing the issue, but the problem continued. Now the deployment is stuck on “Applying 20 changes” and won’t finish. This appears to be a Railway-side issue with applying the variable changes. Please investigate the GODDESS service and resolve this as soon as possible.
Attachments
1 Replies
15 days ago
The GODDESS service carries 68+ numbered ACCOUNTS_* variables, which is a pattern of storing data payloads in environment variables rather than using them for configuration and secrets. When the environment grows this large, staged-changes applies are killed because the total variable payload exceeds an internal size ceiling, which is why your "Applying 20 changes" never finishes. The earlier stuck apply will settle on its own within a few hours, and the 20 pending deletions you see now are your current staged set ready to try again, but retrying will hit the same wall until the environment shrinks. The fix is to remove the bulk ACCOUNTS_* variables and move that data into a connected repo, a published image, a volume, or an object-storage bucket fetched at runtime.
Status changed to Awaiting User Response Railway • 15 days ago
8 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 8 days ago