Each cron execution creates a separate deployment, and you can click on any specific deployment in the Deployments tab to view its logs. If you're looking at logs for a past run, you can also use the Log Explorer (Observability tab) which lets you select a custom date range to jump directly to logs from a specific time period, avoiding the need to scroll. Note that on the Hobby plan, logs are retained for 7 days.

Each cron execution creates a separate deployment? What? Deploying where?

Okay, so clicking on any of those executions (see screenshot below) is by design not giving me the logs for the execution period of that exact run, correct? I still need to check the timing of the exact run I need, then go and check in other place.

From the UI and how it behaves (opens logs when you click on any of cron job past runs) It looks like it should open logs for that exact run, but it opens last available log from the last available run.

You're right, clicking a specific execution in the "Recent Executions" panel does not scope the logs to that run's time window, and the previous reply was incorrect about each execution creating a separate deployment. Cron executions restart the same deployment, so all logs live in one stream. This is a known UX gap. For now, the Log Explorer (Observability tab) lets you set a custom date range to jump to a specific execution's logs. You can submit a feature request for scoped cron logs at railway.com/feedback.

https://railway.com/feedback

Submit a feature request you say...?

https://station.railway.com/feedback