> 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.md).

# Atomyx Submit Troubleshooting

This page helps with common issues encountered when configuring or operating Atomyx Submit.

### Common issue areas

#### Upload failures

Typical causes include:

* file too large
* unsupported file type
* network timeout
* authentication failure

Check file limits, accepted file types, upload timeout behaviour, and API credentials first.

#### Preflight errors

Typical causes include:

* missing fonts
* wrong colour space
* low image resolution
* PDF/X compliance failures

These are usually resolved through a combination of better customer guidance, profile tuning, and production-stage automatic correction.

#### Branding issues

Typical causes include:

* logo file format or size problems
* incorrect colour format
* cached assets
* configuration not saved correctly

#### Proof page generation issues

Typical causes include:

* missing or incorrect proof template
* preflight not actually completing successfully
* incorrect template mapping
* missing order metadata

#### API integration issues

Typical causes include:

* invalid or expired API keys
* webhook or callback URL problems
* incorrect payload format
* timeouts between systems

#### Performance issues

Typical causes include:

* large uploads over unstable networks
* over-complex preflight profiles
* slow preview generation
* overloaded processing capacity

### What to collect before contacting support

If you need help, collect:

* portal configuration details, excluding secrets
* exact error messages
* browser console output
* server or API logs
* a sample file where possible
* workspace ID
* order or artwork ID
* time of failure
* steps to reproduce the issue

### Recommended next step

If the problem is configuration-related, go back to **Portal Configuration**.

If the problem is architectural, review **Submit Architecture**.

If the issue is specific to a real deployment pattern, check **Implementation Patterns**.


---

# 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.md?ask=<question>
```

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.