If you use full automated workflows with PrimeCenter, such as silent mode or XML tickets, production errors can occur without any visible alert. Production reports, generated in CSV format, allow you to track what failed and why, so you can troubleshoot issues.
Enabling production reports
Screenshot PrimeCenter V4.1
- Go to Settings > Production report.
- Enable Generate production reports.
- Configure the following options:
- Report generation interval: Define how often the report should be generated (in minutes).
- CSV separator: Choose the field separator for the CSV file: semicolon (;) or comma (,), depending on your integration requirements.
- Output folder: Select the folder where reports will be saved. Starting from PrimeCenter V4.2, they are saved by default in: Documents/PrimeCenter/Reports/CSV.
Warning
Reports are not deleted automatically. You must remove them manually or use a third-party application to manage cleanup.
Report contents
Each report includes events from fully automated recipes only. This means:
- Files must be imported from a hotfolder.
- Automatic export for print and/or cut files must be enabled.
Warning
Manual or semi-automated operations are not included in the report.
Each CSV file contains the status of the jobs processed up to the moment the report was generated.
Info
File name format: YYMMDD_HHMMSS.csv (timestamp when the file was generated)
You can use these reports to:
- Identify failed jobs.
- Understand the reason for failure.
- Locate the file or recipe involved in the issue.
Status codes
Below is a list of common job statuses and error codes included in the report:
Info
This list is not exhaustive. Some less common errors may also appear in the report.
Success
| SUCCESS | The image was successfully inserted into a layout. |
Import errors
| IMPORT_FORMAT_ERROR | Unsupported or corrupted file format. |
| IMPORT_READ_ERROR | The file could not be read (e.g. due to permission issues). |
| IMPORT_NOT_FOUND | The check/fix profile could not be found. |
| IMPORT_PAGESET_ERROR | The requested page does not exist in the input file. |
| MISSING_IMAGE | The XML ticket points to a file that does not exist. |
| MISSING_PROPERTY | A required property (e.g. from an optical code or annotation) is missing. The debug message indicates which property. |
Nesting errors
| NEST_REJECTED_SIZE | The image is too large to fit the defined format. |
| NEST_NO_CLOSED_CONTOUR | The image has open contours. |
| NEST_CONTOUR_BAD_GEOMETRY |
The image contours are invalid and cannot be processed. |
Export errors
| EXPORT_WRITE_ERROR | The output file could not be written. |
| FOLDER_NOT_FOUND | The destination folder does not exist. |
| FOLDER_ACCESS_ERROR | The destination folder is not writable. |
Preflight errors
| PREFLIGHT_FAILED | A check/fix profile error occurred. |
| PREFLIGHT_PROFILE_ERROR | The check/fix profile is corrupted or cannot be read. |
| PREFLIGHT_XMLREPORT_DIR | The folder for the XML report does not exist or is not writable. |
| PREFLIGHT_PDFREPORT_DIR | The folder for the PDF report does not exist or is not writable. |
Optical code / Cutter errors
| OPTICALCODE_TOO_SMALL | The code is too small to be detected (e.g. QR code dots or Code39 bars are too fine). |
| CUTTER_OPTICAL_CODE_SIZE | The defined format is too small for the cutter’s tracking code and cut marks. |
Other
| CANCELLED |
Processing was cancelled manually. |
| LICENSE_ERROR | A license error occurred. The debug message provides more details. |
⚠️ Known limitation
When using cutters, jobs are marked as SUCCESS as soon as the cut file is queued. If the cutter driver fails later during cut file generation, the error is not reported in the CSV.
This limitation does not apply to print files.