a month ago
Workaround confirmed: railway up (CLI local upload) successfully deploys to a service even though connecting via GitHub source fails with "GitHub Repo not found". So this is specifically a GitHub-source-connection bug, not a general deploy-pipeline issue.
Bug #2 — Dashboard-added variables don't reach the deployed container: Variables added through the web dashboard's "+ New Variable" (and "Raw Editor") showed up correctly in the UI, but never appeared via railway variable list --json nor inside the running container (confirmed via logs: unbound variable). Deleting and re-adding didn't help, and it reproduced on a brand-new service too. Workaround: setting the same variable via railway variable set from the CLI worked instantly and correctly.
Bug #3 — "Run now" fails on a Cron Schedule service: After configuring deploy.cronSchedule (via dashboard Settings, since Config-as-Code railway.json cronSchedule wasn't picked up when deployed via railway up), clicking "Run now" on the Cron Runs tab returns:
Failed to invoke cron execution — We were unable to start your cron execution.
The service itself is healthy (COMPLETED deployment, built and ran successfully once as a regular deploy before cron was configured — confirmed the script fully works end-to-end). It's specifically the manual "Run now" trigger that fails. Not yet confirmed whether the actual scheduled trigger (09:00 UTC) will fire correctly — will report back after it's due to run.
Project ID: 100995bf-3367-46ce-91ec-49a3f4faac73, Service ID (current): please let me know if you need the new service ID, I can provide it.
1 Replies
a month ago
Your cron schedule on conalsur-backup-cron2 is currently staged but not yet deployed, which is why "Run now" fails and the schedule is not active. Dashboard edits (variables and settings like cron schedule) are staged into a changeset and only take effect once you click Deploy on the staged-changes banner at the top of the canvas. railway variable set worked instantly because it commits and triggers a deploy by default (its --skip-deploys flag exists specifically to suppress that). Deploying the pending changeset should resolve both the variable and cron issues.
Status changed to Awaiting User Response Railway • 27 days ago
20 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 • 20 days ago