an hour ago
Hello Railway team,
I'm auditing a scheduled backup service and would appreciate clarification about Railway's cron execution metadata.
I have three questions:
- Is there a way to definitively distinguish a scheduled cron execution from a manually triggered execution using run-specific metadata?
- Can Railway expose the numeric process exit code for an individual cron execution, rather than the deployment's overall status?
- Can the execution window shown in Railway differ from runtime-log timestamps? If so, what do those timestamps represent?
I'm particularly interested in existing read-only dashboard, CLI, API, or audit-log methods.
No configuration changes or reruns are requested. I only need clarification about existing records.
If these details are unavailable, please confirm whether Railway provides an alternative way to obtain them.
Thank you!
1 Replies
an hour ago
None of our public tools (dashboard, CLI or API) have a field that marks an execution as scheduled or manually triggered. The cron execution history lists each run with a start time, an end time and a status (running, exited, crashed, or skipped if the previous run was still going), but it doesn't say what started the run.
We don't expose the numeric exit code for individual executions either. You'll only see the execution status and the deployment status. If you need the exact code for an audit, the most reliable option is to have your backup job print its own exit code and a trigger marker to its logs before it exits.
Yes, the two sets of times can differ. The execution window's start and end times come from our platform's clock. Log timestamps are added when the running container emits each line. Container startup happens before your process prints anything, so the first log line can come later than the execution's start time, and small clock differences between the two are possible too.
Status changed to Awaiting User Response Railway • about 1 hour ago