nxfi777PRO
10 months ago
I have a railway cron container running at 54 minutes past each hour. For some reason, sometimes there is a delay for the container start, and this delay can be very long (for example, this last execution it actually started the job at :06 past the next hour). The container image is not large.
0 Replies
10 months ago
this is likely due to the slowness that deploys have been going out lately
9 months ago
Crons make no guarantee about being "on time". They should fire but there will almost always be some variance