I tried that already. It’s something else. If no one else, with same versions as me, is experiencing these issues, it means that it’s a limitation on my organization.
One workaround that i found was to add an activity to open a normal page like edge//newtab before the open browser that you are using and closing right after.
That way the browser identifies the extension and will work on incognito window
A workaround involves, in the workflow, opening a window incognito, opening a normal window and closing it. This way, for some reason, the extension starts to work correctly during execution.
You returned like Gandalf The White in Lotr Two Towers. My friends, his solution works for some reason. I’ve been doing every known troubleshoot for this issue and it just not works, but the opening and closing of the browser without Incognito option ON fixes it. My clients will be livid.
I am also facing the same issue. Did you get any solution ??
@Palaniyappan@balupad14@Pablito Hi all,
I am facing the issue as mentioned here, “getting an error can communicate with browser”
but my same automation running on if disabled inPrivate mode in studio.
this process is working smoothly on Production( In InPrivate mode) so dont want to face same issue on production.