question

alfiethomas-8724 avatar image
0 Votes"
alfiethomas-8724 asked AndreasBaumgarten answered

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

I am running a simple Monitor Object like the below

101420-image.png


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.

msc-orchestrator
image.png (25.3 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndreasBaumgarten avatar image
0 Votes"
AndreasBaumgarten answered

Hi @alfiethomas-8724 ,

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndreasBaumgarten avatar image
0 Votes"
AndreasBaumgarten answered alfiethomas-8724 commented

Hi @alfiethomas-8724 ,

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

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @AndreasBaumgarten,

Sorry should've been more clear. It was working last week just like you mention. A Incident with classification Sage Test is created or update it fires but today it doesn't with the same creation methods.

The Powershell works fine and this works as expected in the Runbook tester or if I manually click Run on the Runbook.

It is like the Monitor object isn't running correctly.

101472-image.png
101445-image.png
101426-image.png
101493-image.png
101474-image.png


0 Votes 0 ·
image.png (55.3 KiB)
image.png (69.7 KiB)
image.png (44.9 KiB)
image.png (7.5 KiB)
image.png (37.6 KiB)