Troubleshooting Import/Export

This guide explains you some common checks to get your Import/Export up and running again.


Error: "We couldn't find any document in the archive."

Solution: This error can happen when you haven't compressed the documents directly. Try to generate the ZIP archive again by selecting and compressing the JSON files directly (do not ZIP the folder itself), then try to upload that archive.


Error: Empty Image URL makes the import hang

Details: If you leave the URL in the image object in JSON as empty, and click on Import now, then the Import process hangs and never finishes.

Example: {“image_field_api_id”: { "origin": {"url":"" } } }

Solution: Import can not accept a blank value in the image URL. It must have a value: a weblink, a local image path, or a Prismic media library image link.


Error: Empty Image field object fails to import.

Details: When you leave the image object in JSON as empty — without the “origin” object inside — the import process fails.

Example: { "image_field_api_id": { } }

Solution: Import can not accept an empty image object. It must be filled with the “origin” object.


Error: Empty origin object inside image object fails import process.

Details:  If you leave the “origin” object empty — with no “url” field inside -> the import will fail.

Example: {“blog_image" : {"origin" : {  }}

Solution: The origin object must not be empty. It must be filled with a “url” field.


Error: Import fails without the “id” field in the content relationship field.

Details: If you do not include the “id” for a content relationship field, a fatal error occurs.

Example: { “category_link": {"wioUrl": "wio://documents/YEoUkhEAACMA6dYG”}}

Solution: Include the “id” in the content relationship field.


Error: Incorrect “id” field in the content relationship field.

Details: If you include an incorrect “id” value in the content relationship field in your JSON, a minor error occurs and a broken link appears in the document.

Example: { “category_link": {"id": "njnvksjnjk","wioUrl": "wio://documents/YEoUkhEAACMA6dYG”}}

Here, the value of "id" is malformed, and the document does not exist in the repo.

Solution: The value of “id” (the filename of the referenced linked document) must be correct and point to a document that exists in the repo.


Was this article helpful?
Not really
Yes, Thanks

Can't find what you're looking for? Get in touch with us on our Community Forum.