External Dependency Issue

Discussion created by Tony_Watt_7093 on Apr 25, 2016
Latest reply on Sep 29, 2016 by Pete Wirfs

We have recently moved several thousand jobs onto our production UC4 system (v8) and have noticed something that occasionally occurs with external Dependencies.

As an example say we have 10 processes (A, B, C, D, E, F, G, H, I & J).

All 10 processes are daily, set up on a Schedule that reloads at midnight every day.

All 10 processes are set to become Active at midnight also.

Process A is set up with an External dependency on process J.
It is set to be “Only valid, when activated with the same logical date”

Normally this dependency works fine, but a couple of times in the last week it has been ignored because the system thinks that Process J is not valid for today, because I assume it’s activation isn’t yet complete, and the report for today hasn’t yet been created?

We have many hundreds of processes that start at midnight and so I think this is a timing issue, whereby all the processes haven’t finished activating before the first processes actually start running.
I would have expected that the activation of all processes within one schedule would finish before any Jobs (including the checking of any dependencies) start, but it seems not. 

Has anyone else seen this issue - and if so what can I do to get round it.