Troubleshooting

Most of the small things that go wrong on Fabled have one of three root causes: a stale browser cache, a flaky network connection, or a permissions setting that is doing exactly what it says but not what you expected. This page walks through the symptoms in roughly the order they show up.

The page is stuck on a loading spinner

Most loading spinners resolve in a second or two. If one sits for more than ~30 seconds, in this order:

• Hard refresh the page. Browser cache is the single most common cause. Cmd+Shift+R on Mac, Ctrl+Shift+R on Windows / Linux.
• Open in an incognito / private window. If it works there, the problem is browser extensions or cached state in your normal profile.
• Check the platform status page (link in the footer). Wide-impact incidents post here within minutes of detection.
• If still stuck, open the browser console (F12) and look for red error rows. Even if you cannot interpret them, copy-pasting them into a support ticket gets you a fix faster.

A character or campaign disappeared

Content in Fabled is never silently deleted. If something is missing:

• Check the archive view. Most missing content was archived, not deleted. Archived items show up in the relevant tab on the Characters or Campaigns page; one click restores them.
• Confirm the account. If you have multiple Fabled accounts (test, personal, work), the missing content might live on a different one. Check the avatar in the top-right.
• For a missing character: confirm the campaign you expected it to be in. Characters belong to a campaign; opening the wrong campaign hides characters that exist on a different one.
• If you cannot find it anywhere and you are sure you did not delete it, open a support ticket; the team can recover deleted content within a 30-day window.

A dice roll is not landing

If you click a sheet button or fire from the dice tray and nothing happens at the table:

• Confirm you are connected to the session, not just looking at it. The session header shows Connected or Reconnecting; the latter is a network issue and rolls queue until reconnect.
• Check the dice-tray history. If your roll appears there but not in the chat log, the result is computed but the broadcast is failing. Refresh the page; the queued result will replay.
• If the button is greyed out, the framework is preventing the roll. Hover for the tooltip; common reasons are 'no spell slots remaining', 'already used this round', or 'no target selected'.

Voice or video has dropped

Voice and video are WebRTC; they re-negotiate after a brief disconnect but cannot recover from a long one without a refresh:

• Look at the voice strip. Each member has a connection icon; red means disconnected for them, yellow means rough.
• If only one member is red, they need to refresh on their side. If everyone is red simultaneously, the host had a hiccup; everyone refreshes.
• Browser permission for microphone / camera occasionally drops on update. Check the address bar's permission icons if the page can no longer reach your hardware.

Content from the marketplace is not appearing

If you bought a bundle and cannot find it in your library:

• Confirm the purchase landed. The marketplace order history is on the account page; a successful order has a green status badge.
• Refresh the library after a purchase. The library is cached for performance; a hard refresh forces it to re-fetch.
• Marketplace content has its own filter in the library. Make sure you are not filtered to 'Mine only'.

Reporting a bug the right way

If none of the above resolves the issue, the in-app bug-reporter (the bug icon in the top bar) is the fastest path to a fix:

• It captures your current page, browser version, recent actions, and the last few server requests automatically.
• Add a one-line summary of what you expected vs. what happened. Screenshots help.
• The report goes to the support team and to the engineering on-call channel. Most reports get a first response within a business day; high-impact reports get paged immediately.