Blue Prism Process stuck in Warning status on a deleted VDI

[David_Hanchett]

A bit of an odd one here.

Our IT department deleted a Virtual Desktop that was being used to run BP processes. Because a process was running at the time, it is now showing the Warning status which in turn is blocking the scheduler from running subsequent processes on a different machine.

Does anyone know a way to 'purge' the running process? We can't log into the bot itself because the VDI no longer exists (we've got the same virtual user logged into a new VDI to replace it).

[VanamalaSrinivas]

Hi @David_Hanchett,

One way I could think is to stop the Blue Prism service in runtime servers & any backup servers (if exists), with this session running on the machine should terminate eventually.
if this is in prod env - we might need some downtime during odd hours.

[hossein.azimi]

David_Hanchett

Thank you for contacting Blue Prism Community.

One more suggestion is to use "Pending Session Starter VBO for Blue Prism" in the Blue Prism DX asset site. You can find the link in this asset.

https://digitalexchange.blueprism.com/assets/cardDetails?id=134901

Pending Session Starter VBO for BP version 7.2(+) XBP

Best regards
Hossein Azimi
APJ support team

[david.l.morris]

@hossein.azimi What does the Pending Session Starter have to do with this? Does it have some extra functionality of stopping running sessions? I would expect it would only help with a session that is still pending, but OP clearly stated their issue deals with running sessions.

[SayeedBinAbdullah]

Hi @David_Hanchett 

Have you tried below options?

1. Right click on that session and select Immediate Stop

2. Restart Blueprism service in BP server

[david.l.morris]

@SayeedBinAbdullah This was a fair suggestion, but Immediate Stop unfortunately won't help for a session that is stuck in a Warning state. Warning state means it is stuck on a specific stage, and Immediate Stop only affects the session after the current stage has been completed or throws an exception.

The only way I'm aware of to do this was already mentioned by Vanamala which is to restart the Blue Prism Server service on the app server machine.