For cron jobs to be introduced, I imagine that 24/7 uptime could be made possible (like the previous Always On but hopefully less volatile). For now, you could always add in a webserver and ping it using uptimerobot.com (although I can’t say how short the ping interval would have to be, and I’d expect it’d have to be quite short).
Or, depending on the processes and their performance demand it may be useful to have a second server/shard for your bot (hosted on a “cheap” Reserved VM or somewhere else) which also acts as a proxy (and so, an on-demand pinger) for the reserved VM deployment.
and then you might be able to fix this with kill 1 but IIRC I had to Fork the repl
see if you can similarly configure these to be headless or use Xvfb