2 weeks ago
- last edited
2 weeks ago
by
Michael_S
Hi guys,
Hope all of you are well and have a great week start.
Starting from last week (around Wednesday~Thursday) Blue Prism fails while running to identify properly the fields spied using UI Automation mode.
While trying to check in Application Modeler if the fields can still be visible, they were successfully identified, but while running the whole process, somehow the process remains blocked while trying to access those fields.
The interesting part is that after re-spying the fields using UI-Automation (just to test if a new fresh set of fields would make the cut) the bot still fails.
Just to mention, the process worked properly without any errors more than 2 years and all of a sudden it failed to work anymore.
Please let me know if this is a general issue and/or how it can be fixed.
Much appreciated all your help 🙂
Answered! Go to Answer.
Monday
Edge
140.0.3485.66 (offical build) (64bit)
(I better turn off email notifications on this chain now 🙂 )
Monday
Edge
Version 140.0.3485.66 (Official build) (64-bit)
Monday
Microsoft Edge
Version 140.0.3485.54 (Official Build) (64-bit)
Monday
Edge Version 140.0.3485.54 (Official build) (64-bit)
Monday
We have several clients who are impacted by this issue. We use MS Edge, rather than Google Chrome at all of them. At least one of our clients is on: Edge Version 140.0.3485.54 (Official build) (64-bit)
I will have a look if we have other clients which are on a different version than this.
Monday
After some checking, most of our clients are currently on MS Edge Version 140.0.3485.66 (Official build) (64-bit)
Monday
Microsoft Edge
Version 140.0.3485.54 (Official Build) (64-bit)
Tuesday
Microsoft Edge
Version 140.0.3485.66 (64 bit)
Tuesday - last edited Tuesday
Microsoft Edge
Version 140.0.3485.66 (Official Build) (64 bit)
Tuesday
Edge Version 140.0.3485.54 (Official build) (64-bit)