Hi,
using Deadline 2.7, we work with job dependency chains in the form (example):
[A comp job] --> [b] --> [C movie conversion job]
Now that I’ve translated the whole concept to Deadline 3.0, I figured the following:
- [job A] renders ok,
- [job B] (pending, waits for [job A]), renders ok, frame dependent, is auto-archiving
- [job C] (pending, waits for [job B], does not start at all
Looking at the [job C]'s Job Dependencies, the [job B] is indicated as “Deleted” there, which is wrong. But in the job monitor, the [job 2] is indicated first as “Deleted”, then normally as “Archived”, as intended. So it looks like [job C] gets a wrong status info from its dependencies.
I played with the Job Scan Interval, as recommended in related threads (some links don’t work there, though), but i can’t seem to get the [job C] working the inteded way. A workaround may be to set [job C] to “Resume on deleted dependencies” but it isn’t quite aspired.
This issue would be vital for us for switching from v2.7 to v3.0.
greetings
Marcus
