This might be the trickiest part of any IT administrator's, system engineer's, or even architect's job (when it really goes south). You might see yourself in a pickle from time to time with a Runbook that's not delivering the expected result or that by some sort of hazard is not running at all.
When troubles come, troubleshooting steps in, and you need to know where to find the good and valuable information that will help you solve the issue on hand.
This information might also be useful to share with the IT administrator's team that you might have in your company so that they can also proactively investigate and solve any issue that might come along.
Troubleshooting in Orchestrator operates in common sense and there's no real magic around it. Usually, if a Runbook fails, it's either because of permissions, account expiry, or a service that changed from one server to another (such as an upgrade, for example).
Let's check the list of steps that you should give while troubleshooting...