topic issue with Blue Prism Runtime Resource Self-Healing Utility in Product Forum

issue with Blue Prism Runtime Resource Self-Healing Utility

kiranb25 — Fri, 15 May 2026 15:43:40 GMT

I’ve installed the Blue Prism Runtime Resource Self-Healing Utility and have confirmed the following prerequisites are met:

Blue Prism version 7.4.1
Using PowerShell 5.1
Logged into the machine with the same user that is running the process
Runtime Resource and Login Agent are correctly installed
The Blue Prism connection name has been specified
However, when I run the command in the PowerShell console, I receive the following error:

2026-May-15 10:57:19, ServerName(XXXXXXX1), Runtime Resource Self-Healing not applicable

Would anyone be able to advise what might be causing this error or what else I should check?

@ewilson

Re: issue with Blue Prism Runtime Resource Self-Healing Utility

ewilson — Fri, 15 May 2026 15:48:19 GMT

@kiranb25 I've dropped a note to the submitter of the asset with your question. We'll see what we can find.

Cheers,
Eric

Re: issue with Blue Prism Runtime Resource Self-Healing Utility

stevenooi — Sat, 16 May 2026 11:30:11 GMT

Hi @kiranb25
The "Runtime Resource Self-Healing not applicable" message is not an error.
It is merely indicating that the "healing" is not applicable in the script run dated "2026-May-15 10:57:19" because it found an active and responsive instance of "automate.exe" in memory.
In other words, it did not find any condition that requires a re-activation of the "automate.exe" Runtime process.

Re: issue with Blue Prism Runtime Resource Self-Healing Utility

Jesada — Tue, 19 May 2026 16:11:10 GMT

Hello @stevenooi

I am exploring this dx utility, and it works well at restarting automate.exe whenever the process is not running. But I am having a hard time getting the -rebootiffail to trigger to fix a warning in the control room.

Re: issue with Blue Prism Runtime Resource Self-Healing Utility

Jesada — Tue, 30 Jun 2026 20:45:35 GMT

Has anyone using this been able to get the -rebootiffail switch to actually work? I was so excited to see something designed to identify and fix the warnings but according to testing and gpt, there's almost no circumstances where the -rebootiffail path would be taken. I like the idea of not constantly querying the production database to look for the warning status, so if there was some way to identify them externally from BP (such as looking at the port like in the script) that would be ideal.

Is there a long term fix that I may have missed that will solve all my warning issues? Running chrome and edge and version 7.3.2