An import fails

The errors importing characters, maps, systems, books, music and Foundry, with cause and fix.

Importing means bringing into Roliando something made elsewhere: a character, a map, a system, a book, a music list or a Foundry package. Almost every failure comes from the file (wrong extension, not the expected format, a link that is not public) or from a cap (space, plan). This page gathers them by type of import, with the message you will see and what to do.

Where it is

Each import lives in its own place: the Library for Foundry, adventures and tables (Importing content), the map settings for maps (Importing maps: UVTT, Dungeondraft, Owlbear, Foundry and TaleSpire), the builder for systems (Importing a system: JSON, package, tables and Roll20) and the sheet for characters (Importing characters: D&D Beyond, HexSheet, Roll20 and Roliando). The detail of how each file should look is in File formats for importing.

First of all: three checks

The extension. A scene, a character or a system is imported from a .json; a Foundry package, a world or a pack, from a .zip. If you downloaded a file that the browser renamed, check that it ends as it should.
That it is what it claims to be. "Invalid JSON" is almost always one comma or quote too many. "Not a Roliando package" means the .zip does not carry its roliando.json at the root.
Space and plan. If the notice talks about space or a cap, it is not a file fault: see Storage and quotas and Plans, limits and downgrading.

Characters

D&D Beyond does not read my character. Check that it is public and that the link or number belongs to that character.
Spells or items are missing. They stay unresolved when the book they come from is not in your compendium (D&D compendium and modules).
It will not let me drop the file. It must be a .json.

Maps and scenes

Walls do not fit the map. Adjust the scale and move the walls before applying them.
"A map with an image is needed". Walls are placed over an image: without an image there is nowhere to put them.
"That file is not a JSON." A Foundry scene is exported as .json; check the extension.
A .dungeondraft_pack is not a map. It carries art, not maps: it is imported into the Library (Importing content).

Builder systems

"Invalid JSON." Look at the detail the notice gives: it is usually a comma or a quote.
"The field key is missing." Each field needs its key.
"Not a Roliando package." The .zip must carry roliando.json at its root.

Books and homebrew

"That looks like an edit link." In Homebrewery use the share link, not the edit one.
"Nothing was found to import." The text lacks the hints the importer recognises: check File formats for importing or try another kind of book.
"I cannot bring in another module." You are at your plan's cap; import into an existing one.

Music

The YouTube or Spotify link cannot be read. It must be a public list or a single song.
Tracks are missing from my Spotify list. The ones not found on YouTube are dropped; the notice says how many.
A file will not upload. It is over 60 MB or is not audio; compress or trim it.

Foundry

My .zip will not install. It must carry its system.json or module.json at the root and, on the free account, you cannot already have another system installed.
A region of my world does nothing. It came in switched off because it could not be fully translated: open it as an event zone, read the report and switch it on.
Images of a scene are missing. If it pointed to images outside the .zip, upload them or export the world with its files.
No room for more packages. That is your plan's space (Storage and quotas).

Obsidian and calendar

If you cannot create the token, read the notice the screen gives; if you lost the token, it is not shown again: revoke the old one and create another. A calendar that does not update may be slow, because calendar apps ask for the link only every so often (Obsidian and the sessions calendar).