I have a scenario where upon the completion of one job, another job should start, executed under a different Windows user. However, upon completion of the first job and when the second job is supposed to start, the second job state becomes Faulted with the following error message:
“Could not start executor. A specified logon session does not exist. It may already have been terminated.”
How can this issue be resolved? The first job has the Stop After property configured, and the second job cannot be rescheduled. Are there any potential solutions or workarounds?