> 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/proofsheet-generation-issues.md). # Proofsheet Generation Issues Proofsheet generation problems occur when the file passes through the workflow but the expected proof page is missing, incomplete, delayed, or built with the wrong template. ### Proofsheet not generated #### Typical symptoms * the file passes preflight but no proof appears * the portal remains stuck on a processing state * customers or staff are waiting for an approval asset that never arrives #### What to check * whether the submission actually passed the required processing stage * whether a proof template is configured * whether Atomyx Prepare returned an error during proof generation * whether the relevant submission status updated correctly #### How to resolve it * confirm the file reached the correct status * verify that a proof template is configured for the product type * inspect processing logs for template or rendering failures * confirm proof generation is enabled where required ### Wrong template applied #### Typical symptoms * a proof is generated, but it uses the wrong format or metadata * dimensions, finishing options, or product details do not match the job * the issue only affects specific products or product families #### What to check * product type values passed from the ERP * template mapping rules * the data used to select the correct proof template #### How to resolve it * verify product-type mapping logic * make sure each product category points to the intended template * test the proof-generation call with known product parameters ### Missing annotations or metadata #### Typical symptoms * proof pages are generated but key details are missing * dimensions, finishing marks, or product notes do not appear * template placeholders appear empty #### What to check * the proof template itself * the variable names expected by the template * whether the order system is passing the required metadata #### How to resolve it * verify placeholder names and variable mappings * confirm the source system sends the required values * test proof generation with sample data before using live submissions ### Practical guidance Treat proof pages as an operationally important part of the workflow, not a decorative extra. They should be reliable, traceable, and consistent with the approved production file. ### Related pages * **Create Proofsheets** * **Approval Workflow** * **Portal Setup** * **Preflight Configuration** --- # 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/proofsheet-generation-issues.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.