Joseph Huckaby

Ah yes, so, as I suspected, it's not quite as simple as your suggested change (but it's a start!). There are a number of cases that may result in a...

So, there are actually a bunch of different cases that have to be handled: 1. A "dead job" that timed out due to its remote server going down unexpectedly and...

Should be fixed in [v0.9.52](https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.52). I was unable to test all the cases, but I tested some of them. This is the best I can do for v0, I'm afraid...

This is a sign that your worker server is overloaded, and it cannot maintain the websocket connection to the Cronicle master server. It's possible that the Cronicle process was killed...

There's currently no way to do that, but it's a great feature suggestion. I'll add it to the list. Thank you! 🙏🏻

Try using the docker `--init` flag: https://docs.docker.com/config/containers/multi-service_container/ > The `--init` flag inserts a tiny init-process into the container as the main process, and handles reaping of all processes when the...

Hey Mark! I'm so glad you are using the plugin parameter system so heavily! That's a great idea. It might be difficult to retrofit this onto Cronicle v1, which is...

Got it, thanks! Yeah, v2 does away with the "feature" that temporarily saves the current event "edit state" in localStorage (browser), and restores it when you come back to the...

I've also disabled that awful feature in [Cronicle v0.9.47](https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.47), which just dropped.

There are 3rd party docker images you can use, but an official one is definitely coming in v2. Until then, check out: https://github.com/cronicle-edge/cronicle-edge