search

ironmansoftware / universal-automation

Universal Automation is the PowerShell-first automation platform.
https://ironmansoftware.com/universal-automation/
MIT License
24 stars 4 forks source link

Some jobs don't show in job history #167

Closed hawkseye76 closed 4 years ago

hawkseye76 commented 4 years ago

Job history for some reason omits recent jobs from history list.

adamdriscoll commented 4 years ago

I think we may have a problem with the groom job pruning jobs it shouldn't big. Do you happen to have a log in C:\ProgramData\UniversalAutomation\logs?

hawkseye76 commented 4 years ago

logs.zip Here is a copy of several days worth of logs with a screen shot of what i see in the jobs screen

hawkseye76 commented 4 years ago

Just kinda watching this for a few day, looks like its cleaning up jobs every hour instead of based on the number of jobs to keep.

adamdriscoll commented 4 years ago

Hey @pshellguruwannabe,

Just a heads up that I haven't been able to reproduce this myself but I've added more logging into the 1.3 version that we just released. I was hoping that you could do me a favor and upgrade to that and grab the logs once again for me to review.

Thanks so much for your help.

hawkseye76 commented 4 years ago

Hey @pshellguruwannabe,

Just a heads up that I haven't been able to reproduce this myself but I've added more logging into the 1.3 version that we just released. I was hoping that you could do me a favor and upgrade to that and grab the logs once again for me to review.

Thanks so much for your help.

Don't mind at all. I don't see the upgrade yet, but when it pops up, i'll run in and put some logs out later.

Thanks

hawkseye76 commented 4 years ago

Here is a log for today. It's still deleting all current jobs hourly. I have my job history set to 50.
I think i see what is going on. I have jobs dated on Apr. 6 still showing up in history for some reason. looks like it might be seeing those, and that is where it's getting the 50 jobs from, but it's deleting the most current jobs instead of the oldest.

log20200416.txt

adamdriscoll commented 4 years ago

@pshellguruwannabe - That's exactly what was happening. Thanks for the help! I've just committed a fix and this will be in v1.3.1