Ok, so complicated title but what I’m describing here is that the runbook is triggered from the Service Manager Self-Service Portal and shows that it’s running with no entry under the log portion of the runbook designer, and it may or may not show that it’s in pending state in the Orchestration Console. Here’s a visual of what I’m talking about:
Thankfully, this is an easy fix. Check your inputs from the Service Manager Self-Service Portal, if you entered &, <, or >, Orchestrator interprets what you’ve entered as a command and freezes execution. You simply can’t use these characters in your Service Manager Self-Service Portal inputs. So remove these, replace them with other character(s) and the problem will go away.
Until next time!
287 total views, 1 views today