@ThomasSasnett - Hey Thomas...our RDA users are encountering this issue more lately as well. We're still researching solutions.
In a call yesterday, it was mentioned this is a communication issue somewhere between users machines and the installed Pega on the user's machine and server-side...thoughts if this is something we can dig deeper into and a direction...?
Branched Information: Originally posted as reply here.
@EricS272 This may be related. I have seen some environments where Chrome or the StartPage just doesn't load fast enough and the adapter is still waiting for it when it reaches the timeout. If you suspect this is the case, try it with a quicker page and see if it is working. You can also try a simple test after a restart of the machine;
Make sure you do not launch any browsers on startup. If some come up automatically, you must ensure all Chrome and MSEdge processes are closed before starting.
Launch the browser in-question and navigate to a web page.
Open Task Manager and switch to the "Details" tab.
Look for the process "OpenSpan.Translators.Web.MessagingHost.exe" to start once your page loads.
Close the browser and (assuming all of the processes close), look for the "OpenSpan.Translators.Web.MessagingHost.exe" to close as well.
If this occurs, your extension is behaving correctly.