The unscheduled for the dependency would show if the dependency isn't found in the schedule based upon its rule (job group/job name and iteration of the job, whether it's matching occurrence or not).
The root cause could be the triggering job is simply not in that day's schedule. However, I've seen this in various versions of TES where you get the message and the job is actually in the schedule and the correct occurrence. This was often just a single day's issue.
If we found it to be multiple days/runs issue then just recompiling the job/group with the dependency will usually do the trick In these instances (not the target job). We'd found that it simply wasn't reading this information when running in the Job Activity Console and recompiling the job allowed it to reread it's definition. You'd think this would not be recurring since the daily compile "should" correct this if it was a simple fluke for the day.
You can check the job in advance to see if the next run shows scheduled or unscheduled if the job is in a future days to consider if you need to recompile it. That'd be my recommendation
