New Cron Experience No Longer Works Unless If I Delete The Service Entirely
So this is how I repeated the steps with the new Cron Experience:
- Enabled New Cron Experience
- Had a couple of Cron skips because of my poor database connections handling
- Disabled New Cron Experience
- Fix the database connections, now working correctly on the Old Cron Experience
- Enable New Cron Experience again and now there is a bunch of backlogged crons "queueing" to finish. The new Cron can now never run unless if I delete every backlogged crons one by one
I don't think this is the intended behavior? Idk if it's possible to terminate all the queuing ones?
2 Replies
Project ID:
07132e98-0ccf-43b8-aa35-1d32c2fdbcfb07132e98-0ccf-43b8-aa35-1d32c2fdbcfb
Update: Huh okay interesting now it actually works. The other runs still say it is waiting for the previous execution but the latest runs are running now
Ok seriously the entirety of this thing may be just my stupidity. The platform works :derp:
It just so happens that the day you thought it would never come and it came and it hit hard and you don't notice
Everything works. Can close this thread now
===
I feel like there can be a little bit more accessibility to why some crons are skipped. I heard the changelog that this was provided, and I'm seeing actual logs being streamed in (for crons that were skipped)
They however just didn't provide enough details as to exactly why it happened. There were no code crashes.
People like me just overlooked the fact that I had stale Redis connections never disconnecting