AnsweredAssumed Answered

Some jobs were not started because they were waiting for themselves

Question asked by RodrigoCunha610921 on Sep 12, 2018
Latest reply on Sep 13, 2018 by sauan03

Hello all,

This is my first topics. I hope I am writing in the right place. 

 

I am using the Java interface 11.2.1 and at moment I am facing a strange issue during a system copy.

Some jobs were not started because they were waiting for themselves. (screen attached)

This strangely happened only in some jobs inserted in diferent jobplans.

This jobs with problme just worked fine in the past inside of the same jobplans. So, it was correctly configured in the past.

 

Did some of you just face this kind of issue? 

 

Thank you!

Rodrigo

Attachments

Outcomes