Summary
This article explains why Dynatrace Browser monitors may fail with 401 Unauthorized errors on challenge‑response pages and how to resolve or work around the issue.
These failures typically occur when applications use dynamic authentication or bot‑protection mechanisms that are incompatible with Synthetic browser execution.
Problem
When executing a Dynatrace Browser monitor:
- The monitor fails with a 401 Unauthorized error
- Execution does not progress past initial request
- Authentication or security challenge blocks the test
This often occurs on:
- Login pages
- Applications with bot protection
- Systems using challenge‑response authentication
Error Behavior
Common symptoms include:
- HTTP 401 Unauthorized responses
- Unexpected redirects or failed navigation
- Monitor unable to load the target page
Cause
This issue occurs because challenge‑response authentication flows:
- Require dynamic interaction (tokens, cookies, JavaScript execution)
- Detect and block automated browsers
- Depend on runtime-generated values that cannot be reused
Dynatrace Synthetic Browser monitors:
- Run with a clean browser session each time
- Cannot persist or replay dynamic authentication tokens
- May be identified as automated traffic
As a result: → Authentication fails, leading to 401 responses
Resolution
✅ Option 1 – Use supported authentication methods
-
Use HTTP authentication in the browser monitor settings.
- In browser clickpaths, Enable HTTP authentication and provide credentials in the Navigate event.
- In single-URL browser monitors, select Advanced setup in edit mode and Enable global login authentication. Then select HTTP authentication and provide credentials.
Read more in Supported authentication methods in Synthetic Monitoring and Configure browser monitors.
-
Additionally, you might need to ignore the 401 status code in browser monitor settings in edit mode. Select Advanced setup and turn on Ignore specific status codes.
✅ Option 2 – Work with application/security teams
If the application uses:
- CAPTCHA
- Bot detection
- Token-based challenges
Consider:
- Whitelisting Synthetic traffic
- Allowing known test endpoints
- Providing alternative authentication paths
✅ Option 3 – Validate behavior outside Dynatrace
Before troubleshooting further:
- Confirm requests succeed in a standard browser
- Identify where the authentication flow breaks
Important Notes
- This is a limitation of challenge‑response mechanisms, not a Dynatrace defect
- Synthetic monitors cannot always replicate:
- Anti-bot protections
- Advanced authentication workflows
When to Use This Guide
Use this article when:
- Browser monitors return 401 Unauthorized
- Pages include advanced authentication or bot protection
- Recording works, but execution fails
Best Practices
- ✅ Test simple, stable endpoints for Synthetic monitoring
- ✅ Avoid CAPTCHA and bot-protected flows
- ✅ Use synthetic-friendly authentication mechanisms
- ✅ Validate clickpaths carefully during recording
What’s Next
If the issue persists:
Provide Dynatrace Support with:
- Monitor URL and configuration
- Execution results and screenshots
- Description of authentication flow
Related reading
📖 Synthetic Troubleshooting Map
📖 Navigate event
📖 Supported authentication methods in Synthetic Monitoring
📖 Configure browser monitors
📖 Ignore specific status codes
