a month ago
Hello Railway Community,
I'm validating the reliability of a scheduled backup service on Railway.
The service has a daily 06:00 UTC schedule. A recent backup execution completed successfully at approximately 06:02 UTC.
However, the execution metadata doesn't clearly identify whether the run was initiated automatically by Railway's scheduler or manually through the dashboard/API.
Is there a supported way to determine the trigger source of a specific Railway execution?
Does Railway expose scheduler-trigger events or audit records that can distinguish automatic executions from manual ones?
I'd appreciate guidance on where to find definitive evidence.
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We don't currently record whether a specific cron execution started from the schedule or from a manual "Run now" in the dashboard or API. Both go through the same trigger, and neither the execution's details nor the workspace audit logs mark which one it was, so there's no record on our side that can tell you definitively.
On timing alone, scheduled runs aren't guaranteed to the exact minute and can start a few minutes late, so a run finishing at about 06:02 UTC on a 06:00 UTC schedule fits a normal scheduled run. That's just consistent with a scheduled run, though, not proof. If you need hard evidence, the reliable option is to have the job log its own context when it starts, for example the start timestamp, so you can compare it against the schedule.
You can see how cron scheduling works in our cron docs.
Status changed to Awaiting User Response sam-a • about 1 month ago
a month 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 • about 1 month ago