2 months ago
Cron is stuck running every 5 mins. I've tried changing and removing the config json. The manual edit is disabled for me.
The graph api call to change it seemed to disable the runs but the dashboard still showed every 5 mins. Then when I changed an env var, the triggers started again (every 5 mins).
6 Replies
2 months ago
The committed config on your service currently reads 0 */2 * * * (every 2 hours), not every 5 minutes. The "manual edit is disabled" behavior happens when a railway.json or railway.toml in your repo sets cronSchedule, since config-as-code always overrides dashboard values and locks the field from manual editing. If your repo still contains a config file with "cronSchedule": "*/5 * * * *", every deploy (including ones triggered by an env var change) will re-apply that 5-minute schedule regardless of what the dashboard or API shows. Remove or update the cronSchedule entry in that file and redeploy to clear it.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
The committed config on your service currently reads `0 */2 * * *` (every 2 hours), not every 5 minutes. The "manual edit is disabled" behavior happens when a `railway.json` or `railway.toml` in your repo sets `cronSchedule`, since config-as-code always overrides dashboard values and locks the field from manual editing. If your repo still contains a config file with `"cronSchedule": "*/5 * * * *"`, every deploy (including ones triggered by an env var change) will re-apply that 5-minute schedule regardless of what the dashboard or API shows. Remove or update the `cronSchedule` entry in that file and redeploy to clear it.
2 months ago
I have removed the cron config in railway.json already. Edit was still disabled. Before that I tried changing the config back to 2 hours but that did not work either.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
I had a session w/ the Agent and it concluded
"the cron is stuck in the UI and won't respond to API changes. This is a platform-side bug that needs their intervention."
2 months ago
Latest chat session with the Agent ended in
I can't create a support thread for you right now. But this is definitely a Railway-side issue — the railway.json is correct, it's being read by the deployment system, and the properties are being mapped, but they're not making it into the final environment config.
You can open a support thread yourself at Railway support with the details above.
2 months ago
I tried deleting the service and syncing it back from our dev environment (dev was working). It still failed.
I had to delete the service and create a new one from scratch.
2 months ago
it look like The cron schedule was stuck on Railway's backend, tied to the service itself, not to the railway.json config.
That's why editing the file, removing it, redeploying, and even API changes didn't fix it. The config was correct the whole time; the platform just wasn't re-applying it to the service.
try to do this
Delete the affected service completely (don't just re-sync it).
Create a new service from the same repo/branch.
Set the cron schedule again in the config file or the dashboard.
Redeploy and confirm it now runs on the correct schedule.
if does not fixed then looks like a platform bug, cron schedule gets stuck on the service level and nothing (config edit, API call, redeploy, resync) clears it except deleting and recreating the service.