System.Net.Sockets.SocketException: Could not resolve host 'pulse-server.decentraland.org'

[sentry]

Sentry Issue: UNITY-EXPLORER-Q31

System.Net.Sockets.SocketException: Could not resolve host 'pulse-server.decentraland.org'
  File "System__11.cpp", line 11497, in Error_11001
  File "System__11.cpp", line 11586, in hostent_to_IPHostEntry
  File "System__11.cpp", line 11997, in GetHostByName
  File "System__11.cpp", line 11838, in GetHostEntry
  File "System__11.cpp", line 11962, in GetHostAddresses
...
(2 additional frame(s) were not displayed)

System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread.

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

[github-actions]

Automated Triage

Issue type	bug
Affected area	Network connectivity / pulse-server communication
Feature category	Primary (Stability & Crashes)
Severity	SEV-2 → 1-high

Reasoning: Unobserved SocketException in finalizer thread indicates a crash issue affecting users (Primary category). DNS resolution failure for pulse-server suggests network/service connectivity problem affecting a subset of users rather than the entire platform. Requires investigation into retry loop (risk of excessive network requests) and exception handling in the pulse-server communication path.

Labels applied: bug, 1-high, web-requests, sentry

---

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

[github-actions]

This appears to be a specific instance of #3654, which covers the broader issue of unobserved exceptions in UniTasks causing crashes.

This issue reports a SocketException for 'pulse-server.decentraland.org' that is being surfaced as an unobserved exception. The root cause is the same: a UniTask is not being properly awaited or forgotten, resulting in the exception being rethrown by the finalizer thread.

Please follow #3654 for updates on the general unobserved exception handling fix, which should resolve this specific occurrence as well.

[github-actions]

Automated Triage

Issue type	bug
Affected area	Analytics/metrics infrastructure (pulse-server)
Feature category	Excessive Resource Usage (Secondary)
Severity	SEV-2 → 1-high

Reasoning: This is a network connectivity issue causing DNS resolution failures for pulse-server (analytics infrastructure). The incident-response docs specifically flag 'Failed analytics events retried indefinitely' as a potential SEV-1 trigger when it affects all users and causes infrastructure cost. However, the duplicate label indicates this is a repeat occurrence of a known issue, and the current 1-high label appropriately reflects either bounded/self-limiting retry behavior or impact to a subset of users. The unobserved exception in the finalizer thread suggests resource leaks in error handling.

Labels applied: bug, 1-high, web-requests, duplicate, sentry

---

Auto-triaged. If labels are incorrect, update docs/issue-triage-categories.md or docs/incident-response.md and re-run triage.