> For the complete documentation index, see [llms.txt](https://docs.atomyx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atomyx.io/atomyx-submit/troubleshooting/atomyx-submit-troubleshooting/preflight-errors.md). # Preflight Errors Preflight errors occur when the uploaded file fails one or more quality or compliance checks. These checks exist to protect production quality, but they also need to be explained clearly so that customers and implementation teams can act on them. ### Missing fonts #### Typical symptoms * preflight reports missing or non-embedded fonts * text in previews may not look correct * the customer is unsure why typography has changed #### What it means The PDF contains text that depends on fonts that are not embedded correctly. #### How to resolve it * ask the customer to re-export the file with fonts embedded * where appropriate, use production-stage font outlining instead of relying on editable text * decide whether missing fonts should be treated as warnings or hard failures ### Wrong colour space #### Typical symptoms * files are flagged as RGB when CMYK is expected * colours may not match the customer's expectations * the issue appears repeatedly from the same source workflow #### What it means The document is using a colour model that does not match the intended print output. #### How to resolve it * ask the customer to export using the correct colour settings * allow warnings at upload if you convert colour later in production preflight * use automatic colour conversion in the production stage where appropriate ### Low image resolution #### Typical symptoms * the report shows low DPI values * screen graphics or web images are often the cause * the customer may not realise the visual quality problem until it is flagged #### What it means Images are not detailed enough for the expected print result. #### How to resolve it * ask the customer to replace low-resolution images with better source files * tune thresholds by product type if needed * treat low resolution as warning or error depending on business rules ### PDF/X compliance failure #### Typical symptoms * the report flags non-compliance with the required PDF/X standard * the file may contain unsupported transparency, metadata, or unsupported constructs * production rules require a stricter PDF format than the customer provided #### What it means The file does not meet the production standard expected by the workflow. #### How to resolve it * ask the customer to export using the required PDF/X profile * automatically convert in production preflight where appropriate * decide whether compliance should be enforced early or later in the workflow ### Practical guidance Preflight rules should be chosen carefully. A useful pattern is: * use the upload-stage check for fast, understandable warnings * use the production stage for deeper correction and enforcement ### Related pages * **Preflight Configuration** * **Visualize Errors** * **Submit Troubleshooting** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.atomyx.io/atomyx-submit/troubleshooting/atomyx-submit-troubleshooting/preflight-errors.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.