Upload failed
A catch‑all in the browser uploader when the failure has no useful message. Sometimes a rate-limited init also surfaces under this same short text.
Why this happens
The client maps empty/unknown errors to “Upload failed.” The real cause may be network, 429 rate limits, storage, CSRF, or a canceled request that lost its detail. Prefer the Network tab response body over this label alone.
Diagnose and fix
1. Open DevTools → Network on the failing init / part / complete / from-url call and read status + JSON.
2. Match clearer siblings when present: canceled, finalize, part save, rate limit, whitelist IP, plan disabled.
3. Admin: uploads enabled, not in upload maintenance, storage healthy, proxy timeouts OK.
4. Retry a small file; if only API clients fail, check Member API rates and keys.