Cysharp.Threading.Tasks.UnityWebRequestException: HTTP/1.1 500 Internal Server Error

[sentry]

Sentry Issue: UNITY-EXPLORER-PC0

Cysharp.Threading.Tasks.UnityWebRequestException: HTTP/1.1 500 Internal Server Error
{"error":"Internal Server Error"}
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/WebRequests/ITypedWebRequest.cs", line 29, in MoveNext
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/WebRequests/WebRequestController.cs", line 88, in MoveNext
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/WebRequests/ITypedWebRequest.cs", line 53, in MoveNext
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/WebRequests/WebRequestController.cs", line 129, in MoveNext
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/WebRequests/ITypedWebRequest.cs", line 53, in MoveNext
...
(122 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 / HTTP handling
Feature category	Primary (Stability & Crashes)
Severity	SEV-2 → 1-high

Reasoning: This is a crash in the web request system when the server returns a 500 error. Crashes are classified under the Primary category "Stability & Crashes". The repeated async frames in the stack trace suggest a retry mechanism that may not be properly handling server errors. Although triggered by a server error, the client should gracefully recover rather than throwing an unhandled exception, making this a SEV-2 issue affecting users in production.

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]

Automated Triage

Issue type	bug
Affected area	Web Request System / Network Infrastructure
Feature category	Primary (Stability & Crashes)
Severity	SEV-2 → 1-high

Reasoning: This is an unhandled exception in the web request controller's HTTP error handling. Web requests are critical infrastructure used across login, asset loading, marketplace, and other core systems. A systematic issue in error handling for this layer qualifies as a Primary category crash that can degrade multiple features. The issue affects some users while the platform remains partially functional, meeting SEV-2 criteria.

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.