What happens to the automation activity when a checkpointed runbook restarts?

Stuart_DouglasStuart_Douglas Customer IT Monkey ✭
We're creating a user off-boarding offering that will start an SMA runbook to disable the affected AD user object; however, we're allowing a requesting manager to specify a date/time for termination that can occur in the future. This leaves open the possibility that monthly server patching could disrupt a running runbook. Setting a checkpoint will let it restart gracefully, but I'm curious how the status update back to SCSM will be affected. My suspicion is that the activity wouldn't automatically be updated with the completion status and that we'd have to find a way to do that programmatically within the runbook.

Best Answers

  • Stuart_DouglasStuart_Douglas Customer IT Monkey ✭
    Accepted Answer
    Interesting idea. We could fork the activity flow based on the manager selection for processing ("immediate" or "future"). The "immediate" path would trigger the RB that would do the account disable, while the "future" path would not, and would instead rely on another RB that runs every N minutes checking for open SRs with "future" = $true and doing a date comparison between now and the manager-specified date/time, calling the account disable RB when the time arrives. This could work, thanks!

Answers

  • Stuart_DouglasStuart_Douglas Customer IT Monkey ✭
    Accepted Answer
    Interesting idea. We could fork the activity flow based on the manager selection for processing ("immediate" or "future"). The "immediate" path would trigger the RB that would do the account disable, while the "future" path would not, and would instead rely on another RB that runs every N minutes checking for open SRs with "future" = $true and doing a date comparison between now and the manager-specified date/time, calling the account disable RB when the time arrives. This could work, thanks!
Sign In or Register to comment.