Joseph Huckaby

This looks like classic corruption of the "database" files on disk, which can happen if you use a non-AWS S3 provider. The S3 provider needs to provide "immediate consistency" which...

To fix your issue, try an export, followed by a wipe of all data, then an import. Note that this will lose your job history, as the exported data only...

Sure, the job history is a "list" which is created and managed by my [pixl-server-storage](https://github.com/jhuckaby/pixl-server-storage) module. See this doc specifically which explains how lists work: https://github.com/jhuckaby/pixl-server-storage/blob/master/docs/Lists.md There's one list which...

I should add that enabling [Transactions](https://github.com/jhuckaby/pixl-server-storage/blob/master/docs/Transactions.md) at the storage level will probably help with these issues, as it will rollback to a known good state for crashes and/or power loss....

Cronicle [v0.9.24](https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.24) was just released, which ships with transactions enabled by default (however you'll need to manually enable them for existing installs), as well as a new storage repair script....

Hmmm, I don't know anything about `hostPrefixEnabled`, but it looks like AWS deprecated it in v3: https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/preview/migrating/notable-changes/

I apologize, but there is no way to accomplish this currently. However, this is really a great idea. I'm going to add this to the TODO list for Cronicle v2,...

This sounds like an issue with your cloud provider, or your VPC setup therein. Make sure your servers can connect to each other outside of Cronicle. Use `ping`, `traceroute` and...

Wow, I really cannot fathom how this is possible. An event job completion only inserts one single item into the list. I am struggling to see how they could ever...

This is such a bizarre issue, because each of those jobs has an identical ID in the table. Every job is assigned a unique ID when it is first created....