Hi Michael,

I do not have a resolution to this error. Instead, I've been working around it and initializing the subscription from where the job runs and running it...

This was a very helpful post. Thank you for the advice as well.