Runbook doesn't run when checked in but does in runbook test and manually.

Question

I am running a simple Monitor Object like the below

Which then pulls the Id and places it in the ID field in the powershell here: 101330-powershell-example.txt

This was working but has suddenly stopped for no reason. The environment is a test environment and only I use it. No updates or anything like this has changed. All accounts remain the same and none are locked out.

This all works when I run it manually and even when I run it in Runbook tester.

Any advise on what is going on would be great or anything more I could do to diagnose would be amazing. It was checked in and working last week and now it just sits there and does nothing.

Kind regards,
Alfie.

Answer 1

Hi @alfie thomas ,

just to be clear:
Runbooks with a monitor activity needs to be checked in and running all the time -> Click on Run in the Runbook Designer.

A job instance will be started and is monitoring if the condition of the Monitor is met. If condition is met the next activity in the runbook will be started and a new monitoring job instance is created.

----------

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten

Answer 2

Hi @alfie thomas ,

what do you mean with "stopped for no reason"?
The runbook is not starting at all if an Incident with classification equals "Sage Test" is updated or created?
Or the Monitoring activity is triggered and the .Net Script activity is not working properly?

----------

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten