Eliminate dependency upon parent runbooks pubished before child runbooks
I ran into an issue where I had no idea how to fix nor was the error message correct. I called CopyItemtoVM runbook and got an error saying Connect-Azure runbook could not be found. that was only because I had imported the child CA after the parent CITVM. Error message needs to be updated and more importantly this bug is very hard to figure out.
We are currently investigating how we can fix this issue so that it does not matter what order you publish your runbooks in.
But better error messages to explain the actual issue would definitely help too. I’ll keep you posted. :)