Large HTTP payload

[sentry]

Sentry Issue: UNITY-EXPLORER-PYD

Offending Spans	http - POST /asset-bundle-registry/entities/active
This issue was automatically created by Sentry via Explorer Alpha Github Issue Creation

[github-actions]

Automated Triage

Issue type	optimization
Affected area	Asset Bundle Registry
Feature category	Primary (AssetPacks in Creator Tools & Scenes)
Severity	SEV-3 → 2-medium

Reasoning: The Sentry alert indicates an HTTP payload size issue on the asset-bundle-registry endpoint. Per the excessive resource usage classification, this represents an efficiency problem affecting users during asset operations (deployment, loading). Without evidence of widespread impact, timeouts, or catastrophic infrastructure cost, this is classified as SEV-3 (secondary resource optimization) rather than SEV-2. If investigation reveals this is causing failures or significant cost impact, escalate to 1-high.

Labels applied: optimization, 2-medium, asset bundles, web-requests

---

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

[github-actions]

This is a duplicate of #9990. Both issues report the same Sentry alert about large HTTP payloads on POST endpoints. Please follow #9990 for updates and resolution.

[github-actions]

Automated Triage

Issue type	optimization
Affected area	Asset bundle registry / HTTP payload
Feature category	Primary (Creator Tools & Scenes → AssetPacks)
Severity	SEV-3 → 2-medium

Reasoning: This is an optimization issue where the POST payload to /asset-bundle-registry/entities/active is unnecessarily large, causing excessive bandwidth usage. While AssetPacks are a Primary feature, this specific issue has bounded/self-limiting impact (affects specific API calls, not growing unbound or affecting core gameplay). Per the Excessive Resource Usage policy, this is SEV-3 and handled in the normal release cycle.

Labels applied: optimization, 2-medium, asset bundles, web-requests, sentry, duplicate

---

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