What websites may check
Websites may evaluate:- Browser type and version
- User agent
- Cookies and session state
- Language and timezone
- Screen size or viewport
- IP address and location
- Loading behavior
- Interaction timing
- Repeated request patterns
Why it matters
Fingerprinting can cause tasks to behave differently across environments.| Situation | Possible explanation |
|---|---|
| Works locally but fails in cloud | Website treats the cloud environment differently |
| Login expires unexpectedly | Session or cookie signals changed |
| CAPTCHA appears during runs | Website detected unusual browser or traffic behavior |
| Content differs by run | Location, language, or session state changed |
| Page loads incomplete content | Browser or environment signals affect page behavior |
How to reduce fingerprint-related issues
Control location when needed
Use proxies if the website serves different content by region or IP.
Compare logs
Compare local and cloud run behavior using logs when failures appear only in one environment.
Best practices
- Keep task behavior close to normal browsing patterns.
- Add waits for dynamic content.
- Avoid unnecessary repeated page reloads.
- Use stable sessions for login-required sites.
- Use proxies only when they solve a clear access or location issue.
- Re-test tasks after major website changes.