It seems that some script dependencies are not checked by the pending job scan.
We have the following job:
But searching for the job id in the pending job scan reveals no attempt at handling that dependency:
This is using .32 release candidate.
Actually, it seems like the job id’s are not logged in the pending job scan, so that search would not reveal the check.
Found the check, its actually running but since it had no logging of its own, there were not many lines about it. Would be great if the currently checked job ID was printed somewhere so its easier to find. In this case the script being run was unique to the job, so looking by the pathname worked, but for common scripts shared by multiple jobs we couldnt find the job check in the logs very easily.
I’m sure we could add these print statements in if Verbose logging is enabled. I’ll add it to the wishlist.
Cheers,
Ryan