Wednesday
Good day Team,
We have a process that was running fine in production.
Recently we started noticing that from control room the process is going into the warning state, I believe when specifically when interacting with msedge.
Are there any suggestions around handling these scenarios and what can be done to resolve them?
Is this a coding / process issue or infrastructure?
Any suggestions, hints or tips?
Kind regards
Gavin
Wednesday
For context, this KB article explains why a 'Warning' status can occur: "What does a status of 'Warning' mean when displayed in Control Room?"
To troubleshoot this issue in the short-term, I'd suggest to review any recent changes to the environment or the Process itself, including if Edge may have been auto-updated to a new version -- this is the most common reason which can cause the Process to behave differently or execute stages at a different speed than it was designed.
If you've recently upgraded Blue Prism versions, be sure to review the known issues for your specific version as well -- some examples in v7.x versions below:
Wednesday
Thank you, Steven, for the relative links, I will get the Devs to investigate with our Infrastructure team to see if they can resolve
Thursday
I'd be curious what it is doing at the time and what days of the week this happens on. For us, the only time I've seen processes get stuck when interacting with Edge is when an Edge update gets triggered. But I think our situation is rather niche. We have an automation go to the About page to trigger update checks and then click the Restart button that shows up in Edge. And at that point, it gets stuck, specifically using v7.5.1. But I haven't seen anything get stuck otherwise unless there's a popup of some kind.
Thursday
Thank you, David, for your advice