mikeTWC1984

That's normal. If user is limited to category/server, he won't have access to job log details. He only could see some very basic info from run history. The reason it's...

You can achieve that by checking "catch up" box. The only thing - you should start the job via scheduler (not manually). In this case your job will keep re-runing...

Yes, I think it's a good approach to populate some id in chain data. Then just poll "all active jobs" api and check if any of them contain your key....

Nah, out of the box Cronicle can only use it's own auth. You can also set up external auth, but it should be configured to mirror Cronicle auth api (like...

This would require some source code update. I'll share some code later

Here is the updated user module I created for my fork to enable AD auth https://github.com/cronicle-edge/cronicle-edge/blob/main/lib/user.js In order to use it within existing cronicle: - copy this user.js file to...

Check the log file, last several lines should contain detailed error description. I'd think this is something related to permissions (like the user running cronicle doesn't have write permission on...

I assume your cronicle crashes once you see error 500, so that js error should pop up somewhere in the log. Do the following: ssh to your server, stop cronicle....

OK, so the cronicle itself is not crashing, just can't setup a connection. Try to copy this url to your browser: http://cronicle-server-testing-dev.com:9000/api/app/config If you are getting response then that it...

OK, just for sanity check you may try default port 3012 Also, try to go to http://cronicle-server-testing-dev.com:9000 and then in browser's console run this: ``` var socket = io('ws://cronicle-server-testing-dev.com:9000'); socket.on('connect',...