12-04-21 04:17 PM
12-04-21 04:45 PM
12-04-21 06:07 PM
15-04-21 04:51 PM
15-04-21 10:01 PM
19-05-21 02:55 PM
19-05-21 03:06 PM
21-12-21 03:38 PM
21-12-21 04:03 PM
@bbobo I'm surprised to hear that killing automate.exe fixes the issue for you. I'll need to think about that one or maybe try it.
(Edit: Below I mention that we do not usually have the issue you described, but what I mean is that it's far less common than it used to be, but I do get the extension detected issue typically once a week on one machine or another and on my machine that I develop on. It seems to happen more frequently on my development machine when switching between Control Room and DEBUG mode runs.)
We're using 6.10.1 now, and we "usually" do not run into this issue. Granted, some things to note...
1. We use primarily MS Edge, though Edge is essentially Chrome now so they typically have the same issues.
2. We have begun to avoid using Kill Process on the browser because Blue Prism for a while has had difficulty with properly releasing the port used to communicate with the browser in some situations. We have an action that more gracefully closes MS Edge whenever it needs to be closed by using the three dots at the top right and then clicking Close inside the context menu popup.
3. We use Fixed Port mode. I have not been testing or using Ephemeral Port mode at all for months now because I just haven't had time for testing outside of my normal work.
In any case, I believe that the issue has been fixed or at least is much better in 6.10.3. If you're having issues with this a lot, I'm gonna go ahead and be that guy who suggests to upgrade. If we were having that issue every day, we'd upgrade as well. The only reason we haven't is due to the significant effort in upgrading Blue Prism across our 4 environments and properly testing automations to verify they will work in the target version etc.
I personally tested 6.10.3 on my home machine using both ephemeral port mode and fixed port mode when it was first being released, and it had one feature update that was particularly focused on making sure the port is released.
There's also v7 to consider which uses a different method of browser communication too. We haven't upgraded to v7, but that's mostly again due to the effort involved in doing so but we will likely do it within the next year.
21-12-21 04:12 PM