8 hours ago
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
2 hours ago
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:
a minute ago
Thank you, Steven, for the relative links, I will get the Devs to investigate with our Infrastructure team to see if they can resolve