To investigate possible reasons, why your e-paper was not imported successfully, you might find the first answer, when analysing your imported data via Purple Monitoring Server.

To do so, check the message in the column 'Status'

Check in the column 'Publication date' in Monitoring Server, if the date is in the future.

--> Yes, the publication date is in the future:

--> No, the publication date is NOT in the future:

--> Click on the button 'Reimport selected' in the top bar in Monitoring Server to trigger a re-import of your issue.



If you already re-imported the content and the Status 'ERROR' still persists, continue with these steps:

Also, if you are importing a plain PDF (not an EPUB) as a Zip file, please ensure that the compression is correct. Simply changing the file extension is not sufficient.

--> Make sure, that the publication is spelled correctly: Go to the import CSV file and make sure, that the publication is written in exactly the same way as the Publication you created in your team in Purple Manager.

--> Make sure Import CSV requirements are met: Check, if your Import CSV file matches the requirements listed here: Import CSV requirements

--> Make sure, that none of this common configuration mistakes was applied in your Import CSV file:

--> Make sure, that the PDF file is not broken and meets the Requirements for PDF imports

--> Make sure, that the EPUB file is not broken: Download the ePub file and try to open with Apple eBooks app. If it does not open, it is broken

--> Make sure, that the EPUB file meets the requirements: If you can download AND open the ePub file, validate that it meets the XML (EPUB) Specification

It may be possible, that the publication mentioned in the import CSV file does not match the naming convention of the Publication created in the Purple Manager team. This could be caused by spelling mistakes or wrong upper and lower case letters.

If you have checked your imported data in Purple Monitoring Server and the message in the column 'Status' was 'IMPORTED' it may be due to the following errors:

--> Make sure, that the Issue has been activated for preview and release:

--> Make sure, that there no duplicated publication in Purple Manager:

It might be, that there is a second publication with the exact same name in your Purple Manager team. If this is the case, rename or delete the "wrong" publication. 

--> Make sure, if the issue with the exact filename (.pdf/.zip) can be found:

If your file can't be found in one of both folders, it wasn't delivered on sFTP

If you can find the file it was delivered on SFTP. If it was anyways not imported, check if the name of the output matches with the Import CSV file:

This implies that you have written the wrong file name in the CSV. If this is the case, please correct the mentioned file name to e.g. PDF or ZIP. 

If the File was delivered and the CSV file is correct:

--> Make sure, if the PDF file isn't broken or does meet requirements: This can lead to an import error.

--> Make sure, if the EPUB File isn't broken (in case you use Readmode):

If the EPUB file can be opened:

--> Make sure, if your ePub file meets the requirements: Check for the XML (EPUB) Specification

If you have one or more CSV files stored in a folder that reference the same data, the import process will not start. Certain combinations of entries should not be referenced in multiple CSV files or entries.

--> Make sure you haven't store or more CSV files stored in a folder that reference the same:

To solve the problem, move one of the CSV files in the sFTP Server to a subfolder and place the associated files there. This ensures that the imported data is unique and prevents conflicts.

Ideally, an issue name should not be referenced in several entries or in several CSV files. 

--> Make sure, to have run the import via one single CSV and entry: If you import several versions of an issue, e.g. an evening edition with a different file name but the same issue name this can also lead to errors.