Intermittent issues with browser monitors on Windows Synthetic Activegate v1.307

We're investigating reports of Windows ActiveGate 1.307 synthetic monitors experiencing intermittent errors. We will continue to provide updates as they become available.

We are still actively investigating the issue, and we hope to share an update soon.
We appreciate your patience while we work to resolve this issue.

We have deployed an updated synthetic module to all customers, which should lower the failure rate of synthetic tests. In the meantime, we keep investigating the issue and working on a permanent fix.

We appreciate you patience and understanding. Please feel free to reach out to us via in-product chats or support tickets for any further questions.

If you are using Synthetic Windows Active Gates and have recently updated to version 1.307 and facing Synthetic failure rate errors, we can suggest to update to latest version of ActiveGate (1.307.47.20250219-043616) that is confirmed to reduce the failure error rate of synthetic tests.

However, if further issues may still occur, we can offer a workaround through a support ticket. For any further questions, please feel free to reach out to us via in-product chats or support tickets.

There is a Community article for this issue here:
https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Intermittent-issues-with-browser-monitors-on-Windows-Synthetic/ta-p/270969

We appreciate your patience and understanding as we continue our investigation.

We are still investigating this issue and working towards a permanent fix at this time. A workaround is available and more information can be accessed on our Community article.

We appreciate your patience as we work to resolve this.

We have identified the potential root cause of the issue and are currently evaluating various solutions to implement a permanent fix.

A workaround is available and more information can be accessed on our Community article.

We appreciate your patience and apologize for any inconvenience this may have caused.

After identifying the root cause, we are in the process of deploying a fix that cover the issue in the version
1.307.54.20250303-144135

We appreciate your patience and regret any inconvenience this may have caused.