Last updated: June 08, 2026 (Europe/Berlin) Audience: Minecraft Bedrock client devs, LiveOps, QA, support engineers
Disclaimer
- Named error codes (e.g.,
Drowned,Creeper,Breeze) are documented in the Minecraft Help Center.- Marketplace letter-number codes (e.g.,
B-0010,C-0010,SD-002-0) have only partial public documentation. Most meanings below are derived from observed in-game UI text, Mojira bug reports, and player impact patterns.- Treat letter-number codes as operational signals (what to tell the player + whether retries help), not as a stable backend API contract.
- PlayFab backend / redemption errors are official API-layer errors. They are useful for logs, support correlation, and entitlement debugging, but they are not the same thing as player-visible Bedrock dialog codes.
- Overview
- Quick Reference
- 2.1 Marketplace code families (letter-number codes)
- 2.2 Named error codes (Bedrock general)
- Marketplace Error Codes (Detailed)
- Named Error Codes (Detailed)
- PlayFab Backend and Redemption Errors
- Not Included Yet
Minecraft Bedrock Edition uses PlayFab-backed online services for Marketplace catalog/content delivery,
entitlements, inventory, and Character Creator/Dressing Room. When these calls fail, the client often surfaces
short Marketplace-style codes (for example B-0010 or C-0010) instead of raw HTTP status codes or PlayFab enums.
This README groups those codes by player-visible behavior so you can:
- identify the failure class quickly,
- decide whether to retry automatically,
- provide clear player guidance.
Notes:
- The same code may show slightly different text per locale/platform.
- Many failures collapse into a small set of “can’t connect / restart / try later” screens.
- For engineering triage, always capture: platform, locale, build, sign-in state, and whether Realms/Servers also fail.
| Code / Family | Player-facing symptom / typical in-game text | Likely root cause class | Retry hint |
|---|---|---|---|
A-0010 |
Preview build: “Store is unavailable in Preview.” | Preview/Beta environment restrictions, build gating, env mismatch | No retry (switch build / flow) |
A-200 |
Marketplace blocked early (often reported on consoles) | Account/storefront entitlement handshake failed (low-confidence) | Retry after re-auth |
B-0010 |
“We are still trying to connect. Please wait.” | Marketplace endpoint timeout / transient network / service reach | Safe to retry with backoff |
C-0010 |
“We ran into an error. Please restart the game and try again.” | Session validation / account state / entitlement fetch failed | Retry after restart + re-auth |
C-2010 / C2010 |
Marketplace + skins won’t load (reported as C2010 variants) |
Same bucket as C-0010 |
Same as C-0010 |
D-0010 |
“We had an issue connecting. Please go back and try again.” Often + Dressing Room breaks | Broad connectivity failure to online services / routing / outage | Retry later; local steps sometimes help |
D-0020 |
Marketplace, multiplayer, skins, or Dressing Room fail together | Strong D-* connectivity variant; may replace/surface near D-0010 |
Treat like D-0010 |
E-0010 / e-0010 |
Reported as “E-0010” in some tickets; often overlaps with D-0010 screens |
Likely same connectivity family (ambiguous in field reports) | Treat like D-0010 |
E-0020 |
Marketplace/account-state failure; sometimes co-reported with sign-in/session trouble | Marketplace/account-state variant (medium confidence) | Restart + re-auth; retry later |
F-0010 |
“We can’t detect an internet connection.” (commonly reported on Xbox/console) | Console network detection / captive portal / network layer issue | Retry after network reset + relaunch |
L-404 / L-4xx |
Marketplace page/deep link fails; often “trouble connecting… try again later” | Marketplace content fetch failed: service issue OR item not usable | Retry later; may be server-side/content-gate |
L-500 |
Marketplace fails early while loading | Likely L-* service/content-fetch failure (medium-high confidence) |
Retry later; treat clusters as service-side |
SD-002-0 |
“Hmm, Marketplace is having some issues, please try connecting later.” | Commerce/Marketplace backend degraded / maintenance | Retry later; nothing local |
U-000 |
“We’re having trouble connecting to the Marketplace right now. Please try again later!” | Marketplace request failed / connectivity / transient backend | Retry later; backoff helps |
Legend:
- Safe to retry: Automatic backoff + retry is reasonable.
- No retry: Retrying won’t help until the environment/build/account is fixed.
- Retry later: Usually Mojang/Microsoft-side issues or maintenance windows.
These named codes are documented in the Minecraft Help Center and are separate from Marketplace letter codes. They appear across sign-in, Realms, and gameplay flows.
| Named code | Typical context | Likely cause (Help Center) | Quick guidance |
|---|---|---|---|
| Armor | Skin / character creator issues | Issue with the active skin | Switch to a valid skin; retry |
| Arrow | Realms connection | Error connecting to a Realm | Retry; follow Realms troubleshooting |
| Bamboo | Microsoft account sign-in | Sign-in issue | Reset sign-in; restart device; retry |
| Bat | Multiplayer / server disconnect | Disconnected from server | Reconnect; check network |
| Blaze | Sign-in (often on Realms) | Sign-in/session issue | Sign out/in; ensure account is stable |
| Block | Data transfer | Problem sending or receiving Minecraft data | Retry; check network and service status |
| Boat | Realms / multiplayer join | Unspecified error | Retry; check account/network state |
| Breeze | World join | World is newer than the client | Update Minecraft |
| Cauldron | Authentication server timeout | Auth servers not reachable / timed out | Retry; check network; restart |
| Chain | Multiplayer version mismatch | Server/player is on a different Minecraft version | Update/downgrade to match the server/player |
| Chest | Storage | Not enough storage space | Free space; retry |
| Creeper | Microsoft account sign-in | Authentication server / sign-in issue | Reset sign-in; retry; check service status |
| Crossbow | Sign-in | Sign-in error | Sign out/in; restart; retry |
| Deep Ocean | Minecraft Launcher sign-in | Launcher sign-in issue | Restart Launcher; reset sign-in; retry |
| Drowned | Microsoft account sign-in | Sign-in issue associated with Microsoft account | Reset Microsoft sign-in; retry |
| Emerald | World connection | Generic connection failure | Retry; general troubleshooting |
| Ghast | Sign-in / credentials | Problem with credentials | Sign out/in; verify credentials |
| Glowstone | Sign-in process | Error during sign-in process | Restart; reset sign-in; retry |
| Pufferfish | General process flow | Official named error; public summary incomplete | Retry; collect context if persistent |
| Terracotta | General | Unspecified error | Retry; collect context and check service status |
Category: Preview/Beta build gating / environment restriction
Typical player message / situation:
- Preview builds show: “Store is unavailable in Preview.”
What it usually means:
- This build/channel does not have access to the standard Marketplace flow (or requires a Preview-specific flow).
Symptoms:
- Marketplace disabled or unavailable.
- Realms may also behave differently depending on build/channel.
Player guidance:
- Switch to the current public (non-preview) build.
- Fully sign out, restart the game/device, then sign back in.
Category: Storefront / entitlement handshake failed (low-confidence)
Typical player message / situation:
- Marketplace fails early with
A-200(often reported on consoles).
What it usually means (field inference):
- The platform storefront token / entitlement handshake did not validate correctly.
Player guidance:
- Fully quit Minecraft and relaunch.
- Sign out of the platform account and Microsoft account in-game, then sign back in.
- Reboot the console/device.
- If it persists across many users, treat as service-side.
Category: Marketplace service unreachable / timed out
Typical player message / situation:
- “We are still trying to connect. Please wait.”
What it usually means:
- Marketplace data could not be downloaded (timeouts / reachability issues).
- Often transient, but can correlate with ISP routing problems or regional incidents.
Symptoms:
- Marketplace home never loads.
- Dressing Room cannot pull cosmetics.
Player guidance:
- Fully quit Minecraft and relaunch.
- Check internet / try a different network.
- Settings → Storage → Clear Marketplace Cache, then fully restart Minecraft.
- If persistent on console: reboot device; consider reinstall as a last resort.
Category: Session validation / account state / entitlement fetch failed
Typical player message / situation:
- “We ran into an error. Please restart the game and try again.”
What it usually means:
- The client couldn’t validate session/account state strongly enough to load Marketplace and/or owned cosmetics.
Symptoms:
- Owned skins/Character Creator items won’t load; default skin fallback.
- Marketplace and/or multiplayer may be impacted depending on the underlying failure.
Player guidance:
- Fully quit Minecraft and relaunch (this is the most consistent first step).
- Clear Marketplace cache (Settings → Storage → Clear Marketplace Cache), then restart.
- Sign out of Microsoft account in Minecraft, restart, then sign back in.
- If persistent, check for broader outages; treat as service-side until proven otherwise.
Category: C-* family variant
Typical player message / situation:
- Marketplace and skins won’t load; code shown as
C2010/C-2010.
What it usually means:
- Same bucket as
C-0010in field reports: session/account validation and cosmetics entitlement fetch failures.
Player guidance:
- Same checklist as
C-0010.
Category: Connectivity failure across online services
Typical player message / situation:
- “We had an issue connecting. Please go back and try again.”
- Often correlates with Dressing Room not loading and other online features failing.
What it usually means:
- The client cannot establish a working connection path for Marketplace/online services (may be outage, routing, NAT, firewall, DNS, or regional filtering).
Symptoms:
- Marketplace fails.
- Dressing Room / Character Creator may fail to load.
- Servers/Realms/invites may also fail for the same user/session.
Player guidance:
- Try again later (this is often transient).
- Reboot router + device; try another network/hotspot to isolate ISP/router issues.
- Clear Marketplace cache; restart Minecraft.
- Advanced (PC): flush DNS; try different DNS; verify firewall rules for Minecraft.
Category: Connectivity / online services variant
Typical player message / situation:
- Marketplace, multiplayer, skins, or Dressing Room fail in the same session.
- Field reports strongly overlap with
D-0010, and at least some reports describeD-0010as now surfacing asD-0020.
What it usually means:
- Treat as a
D-*connectivity family code unless stronger evidence differentiates it. - The failure may be local network/routing, account session instability, or a broader service incident.
Player guidance:
- Same checklist as
D-0010. - If many users report it at the same time, treat as service-side first.
Category: Ambiguous; likely D-* family
Notes:
e-0010is referenced in some reports, but in practice it often overlaps withD-0010-style “issue connecting” screens.
Working assumption:
- Treat as a connectivity family code until stronger evidence differentiates it.
Player guidance:
- Same checklist as
D-0010.
Category: Marketplace / account-state variant (medium confidence)
Typical player message / situation:
- Marketplace or account-backed UI fails to load.
- Often appears near sign-in, session, or Marketplace availability trouble.
What it usually means:
- Field reports point to a Marketplace/account-state failure, but the exact public meaning is not stable enough to treat as official.
Player guidance:
- Fully quit Minecraft and relaunch.
- Sign out of the Microsoft account in Minecraft, restart, then sign back in.
- Clear Marketplace cache and retry.
- If reports cluster across users/platforms, treat as service-side.
Category: “No internet detected” screen
Typical player message / situation:
- “We can’t detect an internet connection.”
- Often reported on console Marketplace.
What it usually means:
- The game’s network check fails (not necessarily true “no internet”; can be captive portal, DNS issues, Xbox/console network stack edge cases, blocked endpoints).
Player guidance:
- Verify device network status; resolve captive portal if present.
- Power-cycle router/modem; reboot console.
- Try switching network (hotspot) to isolate ISP/router.
- Fully quit and relaunch Minecraft after network is stable.
Category: Marketplace content fetch failed (service-side OR content availability)
What we see in the wild:
- Can appear while the Marketplace is loading, often with “trouble connecting… try again later.”
- Also appears when a specific Marketplace page or content deep-link cannot be loaded.
What it usually means:
- A Marketplace content request failed. This can be:
- transient backend/service issues, or
- the content is not available/usable on this platform/account (platform restrictions, delisting, entitlement mismatch).
Player guidance:
- Retry later; relaunch once.
- Sign out/in to refresh account state.
- If it is tied to a specific pack/skin across many devices, treat as server-side/content-gating.
- If restrictions are suspected, verify “usable everywhere”/platform compatibility within Marketplace UI.
Category: Marketplace load failure
Typical player message / situation:
- Marketplace fails early while loading.
- Reports overlap with the broader
L-*content-fetch / service-failure family.
What it usually means:
- A Marketplace service or content request failed before the UI could complete loading.
- This is more likely to be backend/service-side when many users see it at once.
Player guidance:
- Retry later; relaunch once.
- Sign out/in to refresh account state.
- If widespread, do not over-index on local fixes; treat as service-side.
Category: Marketplace backend degraded / maintenance
Typical player message / situation:
- “Hmm, Marketplace is having some issues, please try connecting later.”
What it usually means:
- Marketplace/commerce backend is degraded, under maintenance, or blocking requests.
Player guidance:
- Nothing local to fix. Try again later.
Category: Marketplace request failed (generic)
Typical player message / situation:
- “We’re having trouble connecting to the Marketplace right now. Please try again later!”
- Can appear in Marketplace sub-views (e.g., Wishlist) while other areas may partially load.
What it usually means:
- A Marketplace request failed mid-flow (connectivity, backend transient, throttling, or session instability).
Player guidance:
- Try again later; relaunch.
- If it persists: reboot network, re-auth Microsoft account, clear Marketplace cache.
- Treat widespread reports as service-side.
These are official, named Bedrock error codes and are not Marketplace-specific.
- Meaning: Issue with the active skin.
- Guidance: Switch to a valid skin in the Dressing Room and retry.
- Meaning: Error connecting to a Realm.
- Guidance: Retry; follow Realms connection troubleshooting.
- Meaning: Microsoft account sign-in issue.
- Guidance: Reset Microsoft account sign-in in Minecraft; restart device; retry.
- Meaning: Disconnected from a server.
- Guidance: Reconnect and validate network stability.
- Meaning: Sign-in/session issue.
- Guidance: Sign out/in; ensure account is stable; retry.
- Meaning: Problem sending or receiving Minecraft data.
- Guidance: Retry; check network stability and service status.
- Meaning: Unspecified error; field reports often mention Realms or multiplayer join flows.
- Guidance: Retry; validate account state, network stability, and Realms/service status.
- Meaning: World version is newer than the client.
- Guidance: Update Minecraft and retry.
- Meaning: Authentication servers not reachable or timed out.
- Guidance: Retry; check network connectivity; restart.
- Meaning: Version mismatch between the server/player and the local Minecraft client.
- Guidance: Update Minecraft, or match the server/Realm version before joining.
- Meaning: Not enough storage space to proceed.
- Guidance: Free device storage and retry.
- Meaning: Problem signing in with a Microsoft account or reaching authentication servers.
- Guidance: Sign out/in, restart Minecraft, retry later, and check for authentication-service incidents.
- Meaning: Sign-in error.
- Guidance: Sign out/in, restart the game/device, and retry.
- Meaning: Minecraft Launcher sign-in issue.
- Guidance: Restart the Launcher, reset sign-in, and retry.
- Meaning: Microsoft account sign-in issue.
- Guidance: Reset Microsoft sign-in in Minecraft and retry.
- Meaning: Generic connection error to a world.
- Guidance: Retry and use general connection troubleshooting.
- Meaning: Problem with sign-in credentials.
- Guidance: Sign out/in, verify credentials, and retry.
- Meaning: Error during the sign-in process.
- Guidance: Restart Minecraft, reset sign-in, and retry.
- Meaning: Official named error; the public short summary is currently incomplete in search snippets.
- Guidance: Retry, collect platform/build/sign-in context, and correlate with nearby service or account issues.
- Meaning: Unspecified error.
- Guidance: Retry, collect context, and check service status if it persists.
These official PlayFab Economy v2 / redemption errors are mainly useful for developers, proxy logs, support correlation, and entitlement debugging. Keep them separate from the player-visible Bedrock Marketplace and named error codes above.
PlayFab redemption APIs may also pass external store failures through errorDetails as MarketplaceErrorCode.
When that happens, correlate the API-layer error with the player-visible Marketplace code and platform logs.
| Code name | Numeric code | Typical layer | Meaning | Triage guidance |
|---|---|---|---|---|
AccountNotLinked |
1014 |
Account / entitlement | Platform/store account is not linked to the required entity or account context. | Check account linking, entitlement ownership, and platform account identity. |
InvalidXboxLiveToken |
1188 |
Xbox / Microsoft Store redemption | Xbox token is invalid during redemption. | Refresh Xbox/Microsoft auth and retry with a valid token. |
XboxXASSExchangeFailure |
1306 |
Xbox auth exchange | Xbox XASS token exchange failed. | Treat as Xbox auth/service integration failure; collect auth traces. |
XboxInaccessible |
1339 |
Xbox service reachability | Xbox service could not be reached. | Check Xbox service status, network reachability, and retry later. |
InvalidPSNAuthCode |
1092 |
PlayStation redemption | PlayStation auth code is invalid. | Refresh PSN auth and retry with a valid authorization code. |
NotAuthorized |
1089 |
PlayStation redemption | Authorization failed in the PlayStation redemption flow. | Verify account permissions, token scope, and entitlement context. |
InvalidCatalogItemConfiguration |
4015 |
Catalog / product config | Product or catalog configuration does not match the redemption flow. | Validate catalog item configuration, store mapping, and platform product setup. |
The following candidates are intentionally not part of the main catalog yet:
L-400andL--2122640862: field evidence is currently too thin or inconsistent.- Creator / Script API HTTP runtime errors such as
InternalHttpRequestError,MalformedHttpRequestError,HttpRequestBodyTooLargeError,HttpRequestLimitExceededError,HttpRequestNotAllowedError, andHttpsOnlyError: these belong in a separate developer appendix if the project scope expands beyond player-visible Bedrock and Marketplace errors.