Hey uh so I decided to write this thread well because I feel like the cronjob expereince has been very odd for me

1. Recent Execution disappears when I remove a cronjob instance

Sometimes my cronjob hangs indefinitely (either my code or who knows what happens), and I typically will remove it to prevent incurring idle RAM costs. BUT, I want to be able to see the logs easily from Recent Executions without getting into the logs tab.

However, I need to redeploy my broken code in order for it to show.

Is there any way to get Recent Executions to continue showing up even if you removed the Cronjob instance?

2. Manually removed instances should NOT redeploy itself after a cron schedule

When I intentionally remove an instance (via Remove), it is typically because of an issue. Even if the cronjob fires, I think it should not automatically redeploy until I press Redeploy myself.

Perhaps a little banner at the top that says something around Instance Is Removed. Redeploy For Cron To Take Effect.

3. Random cronjobs failing to start/produce logs

This issue has been bugging me since I joined Railway in 2022. I realize sometimes my cronjobs just do not want to start and the logs only state Starting Container and nothing else afterwards. It runs the whole duration (with no CPU/RAM usage, but there is idling RAM) until the next cron job replaces it.

I tested the same code locally and it works.

Anyone has this issue?