21 days ago
An existing Bun Function service is healthy, but its source-only patch has remained APPLYING since 2026-10-30 09:41:25 UTC. No new deployment was created; the latest successful deployment is from 06:34 UTC and still serves version 0.5.4.
The saved configuration contains 94 numbered DECE_UI_05x_BUNDLE variables carrying reviewed application code/assets. Twelve were applied with deployments skipped before this source update. The pending Source Code inspector now shows identical old/new bootstrap content.
I found Railway BOT's explanation of the unsupported numbered-file variable pattern here: https://station.railway.com/questions/railway-function-source-accepted-but-not-8b82ce36 . I am preparing to move the release files out of variables.
Please inspect lastAppliedError and the commitChanges workflow for the selected service, confirm whether this particular apply is actually still running, and advise the safe order for migration and variable cleanup. The patch reference ends in fe68. Please preserve the running service, persistent volume/database, saved source and unrelated variables. I have not retried or replaced the in-flight operation.
Full identifiers can be provided privately. No credentials, environment values, customer data or source files are attached.
3 Replies
21 days ago
The apply for the patch ending in fe68 is no longer running. It is now marked as failed, and the only error recorded on it says the operation never settled, with no specific cause. A failed apply here does not mean nothing changed, because configuration writes can land before the apply stops. Please don't retry or restage it.
The cause is the release code stored in the numbered bundle variables, together with a start command that reads those variables, decodes them and runs them. That is not a supported way to ship code on Railway. Each apply carries the whole environment's configuration, so the more encoded payload the environment holds, the more likely applies are to hang or fail. Splitting the code into more or smaller variables will not fix this. The normal encoded Function source on its own is fine.
For the order, move the 0.5.5 release onto a supported source first: a connected repository, or an image you build and publish. Large static assets can go on a volume or be fetched at runtime from object storage. Then change the start command to a short one that runs the deployed files, and confirm that deployment is healthy. After that, remove the DECE_UI_05x_BUNDLE variables nothing uses anymore, and keep your other variables as they are. Removing the bundle variables is what gets the environment applying normally again.
Status changed to Awaiting User Response Railway • 21 days ago
20 days ago
Update after replacing the unsupported code-bundle bootstrap:
I prepared a normal single-file Bun Function (85,216 UTF-8 bytes, under the documented 96 KB limit). It has no custom code evaluation and does not read any numbered code variables. Its static assets are a separate immutable bundle for the existing volume. The exact entrypoint passed 45 isolated checks on Bun 1.4.4.
The source update was accepted, but the new patch ending 37c7 remains APPLYING. Its source/start command and two temporary asset-publishing variables have reached the service configuration.
Updating the normal release-version variable then created a deployment ending 9676. It failed immediately at Initialization (00:00), before Deploy/Network started. Both build and deployment logs are empty, and the diagnosis endpoint provides no failure error or stage detail.
The previous deployment ending 3a80 remains active and still answers as version 0.5.4. The same service and existing data volume are preserved. The 94 legacy numbered code variables have not been removed yet, following the earlier advice to remove them only after a healthy replacement.
Could you identify the initialization failure and confirm whether the pending patch workflow is still running? Please clear or fail a stale workflow if appropriate before another source migration. For now, please advise a supported recovery path without GitHub. An ordinary container entrypoint is also prepared and passed 87 local HTTP checks; its image has not been built or published.
Full identifiers can be provided privately. No variable values, credentials, customer records, or design files are attached to this update.
Status changed to Awaiting Railway Response Railway • 20 days ago
20 days ago
We don't see a reportable staged or applying patch on the production environment right now, so we can't show that the patch ending 37c7 is still running. The service config does already have the new 85,216-byte Function source, which is a normal, supported Function. We have not established why deployment 9676 failed at Initialization, and we don't have an error to point to for it.
The 94 DECE_UI_05x_BUNDLE_* variables are all still on the service. Every apply carries the whole environment's configuration, so while those variables are there, new source or variable applies can keep hanging, even though the new source no longer reads them. Please don't retry or restage the same change on top of them.
That changes the order from our earlier reply. Removing the bundle variables now comes before a healthy replacement, not after one, because the replacement can't deploy reliably while they're still there. The running 0.5.4 deployment still decodes those variables when it starts, so if it restarts or gets redeployed after they're removed, it won't come back on the old code. Plan for that gap before you remove them.
Without GitHub, the supported paths are your single-file Function with assets on the existing volume, or building and publishing your container image to a registry and deploying that image. Keep the asset bundle on the volume or in object storage, not in variables.
Status changed to Awaiting User Response Railway • 20 days ago
13 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 • 13 days ago