This because in VCSP console you can see the Session States dashboard that report workload status and not jobs. In your case workload are correctly backed up from second job.
Why first job not start? Probably there is a wrong condition… I think you’re using this trigger for your remote targets (Cloud connect) or for removable USB drives. Correct?
Is possible first job not starts for connectivity lack (network or usb)? Not knowing the environment, I am clearly speculating….
This because in VCSP console you can see the Session States dashboard that report workload status and not jobs. In your case workload are correctly backed up from second job.
Why first job not start? Probably there is a wrong condition… I think you’re using this trigger for your remote targets (Cloud connect) or for removable USB drives. Correct?
Is possible first job not starts for connectivity lack (network or usb)? Not knowing the environment, I am clearly speculating….
thank you for your answer and for the documentation link.
Mine was just an example scenario, so I don’t have a real-life situation to test this on, but yes, what I imagined was a job destined to an USB drive which only starts when the drive is connected.
