Joseph Huckaby

First let me say, even if you do get the certificates working, Cronicle has several known issues with HTTPS. Many features don't work properly, like the live log system. There...

So, please note that Node.js v12 is rather old, and is no longer supported. Also, you're running an older Cronicle version (it's up to v0.9.3 now). I highly recommend you...

Hello! While this isn't possible with the current version of Cronicle, the next major release (Cronicle 2.0, a.k.a. Orchestra) will allow this through workflows. Basically, you define a workflow as...

I do apologize, but this is currently "as designed" behavior. The Multiplex system launches separate jobs for each target server in the group, and each of those jobs is a...

This will be 100% resolved and handled cleanly in Cronicle v2.0 (Orchestra). Multiplex jobs are now implemented as "workflows" which can be scheduled and chained just like any regular event....

Yup, I'll look into that, thanks.

The live log feature requires a direct connection from the client web browser to the machine running the job. You can control whether it tries to connect via IP or...

Excellent suggestions, thank you! An event failing to run due to server unreachable **should** show on the Activity tab (and it is logged), but I will absolutely make sure this...

Yup, Mike - I came to the same conclusion because categories have settings like default e-mail, default web hook, and default resource limits for jobs. That would become messy if...

> Hopefully in the next version live log would go through the master node (not via direct connection). It will 😊, and also HTTPS/SSL will be fully supported 100%.