Cysharp.Threading.Tasks.UnityWebRequestException: Cannot connect to destination host

[sentry]

Sentry Issue: UNITY-EXPLORER-PAY

Cysharp.Threading.Tasks.UnityWebRequestException: Cannot connect to destination host
  File "/opt/workspace/workspace/a065372e-0c5f-4536-0000-0440104d155d.8c1273e985o/Explorer/Assets/DCL/WebRequests/ITypedWebRequest.cs", line 29, in MoveNext
  File "/opt/workspace/workspace/a065372e-0c5f-4536-0000-0440104d155d.8c1273e985o/Explorer/Assets/DCL/WebRequests/WebRequestController.cs", line 88, in MoveNext
  File "/opt/workspace/workspace/a065372e-0c5f-4536-0000-0440104d155d.8c1273e985o/Explorer/Assets/DCL/WebRequests/ITypedWebRequest.cs", line 53, in MoveNext
  File "/opt/workspace/workspace/a065372e-0c5f-4536-0000-0440104d155d.8c1273e985o/Explorer/Assets/DCL/WebRequests/WebRequestController.cs", line 129, in MoveNext
  File "/opt/workspace/workspace/a065372e-0c5f-4536-0000-0440104d155d.8c1273e985o/Explorer/Assets/DCL/WebRequests/ITypedWebRequest.cs", line 53, in MoveNext
...
(103 additional frame(s) were not displayed)

This issue was automatically created by Sentry via Explorer Alpha Github Issue Creation

[github-actions]

Automated Triage

Issue type	bug
Affected area	Web Requests Framework
Feature category	Secondary (Infrastructure)
Severity	SEV-3 → 2-medium

Reasoning: This is a network connectivity exception ("Cannot connect to destination host") in the web requests infrastructure layer. While network failures can affect multiple systems, without evidence that this blocks Primary features (like login, avatar sync, or chat) or affects most users, this is classified as a Secondary infrastructure issue. The stack trace suggests potential retry behavior — if this is causing uncontrolled retry loops affecting all users, escalate to SEV-2.

Labels applied: bug, web-requests, 2-medium

---

Auto-triaged by Claude Code. If the severity or labels are incorrect, update issue triage categories or severity policy and re-run triage.

[github-actions]

This is a duplicate of #7767, which was reported earlier on 2026-03-24. All instances of this error are related to the same root cause in WebRequestController. Please follow #7767 for updates on this issue.

[github-actions]

Automated Triage

Issue type	bug
Affected area	Web Requests / Marketplace
Feature category	Primary (Marketplace Purchases) — infrastructure-level
Severity	SEV-3 → 2-medium

Reasoning: This is a network-level error ("Cannot connect to destination host") in the web request infrastructure handling payment operations. While Marketplace Purchases is a Primary category, this error is infrastructure-level connectivity issue rather than a feature break. The duplicate marker and existing 2-medium label indicate this affects a bounded set of scenarios or is intermittent/environmental. If this becomes widespread or prevents all payment transactions, severity should be escalated to 1-high (SEV-2).

Labels applied: bug, 2-medium, web-requests, sentry

---

Auto-triaged. If labels are incorrect, update issue triage categories or severity policy and re-run triage.