The upload is rejected
| Message | Cause | Fix |
|---|---|---|
| Unsupported file type | The file is not JPEG, PNG, WebP or GIF, or it is a PDF or PSD export. | Export a flattened raster image and upload again. |
| File is too large | The file exceeds the marketplace cap shown in step 1. | Re-export at the recommended edge length, or upload it and let the resize fix run. |
| Image is too small | The shorter edge is under the marketplace minimum. | Re-export from the source file. Upscaling a small file does not add detail and still fails the quality check. |
| The upload never finishes | A very large batch on a slow connection. | Upload in smaller batches. The wizard keeps the images you already added. |
The inspection stays in progress
A normal run finishes in a few seconds. If the status has not moved after a minute, refresh the page — the status is polled, and a broken poll leaves a stale screen even though the job finished.
- Status failed: the job stopped with an error. Open it to read the reason, then create a new inspection with the same files.
- Status queued for a long time: the run never started. Press Re-inspect to start a fresh round.
- No findings at all on a job with images: check that the images actually attached — the summary counts assets.
The results do not look right
| Symptom | Likely cause |
|---|---|
| Score is 0 but only a few issues are listed | Critical issues cost 15 points each; seven of them reach zero on their own. |
| A rule fired that does not apply to my product | The product category was not set, or was set to a less regulated one. Dispute the finding or run again with the right category. |
| The same issue is reported on every image | It is a per-asset check such as format or metadata. One fix action repairs all of them at once. |
| An issue I fixed is still listed | You are looking at an earlier round. Check the round number on the header, and re-inspect if you edited files outside Dodam AI. |
Downloads fail
- A link that returns an error has expired. Reload the results page to mint a fresh signed link.
- A ZIP that will not open usually means the download was interrupted. Compare the file size against the value shown next to the button and download again.
- Korean characters can be dropped from the downloaded ZIP file name by some browsers. The contents are unaffected — rename the archive after saving.
API calls are rejected
- 1401 — check the header format: Authorization: Bearer dk_live_... with a single space, and confirm the key is not revoked.
- 2403 — the key is valid but lacks the scope, or the job belongs to another organization. Compare the organization on the API keys screen.
- 3400 — read the message; it names the field. Unknown product_category and an unavailable country and platform pair are the two most common.
- 4429 — the monthly quota is used up. Check Settings, then Usage.
Every API response is JSON with a stable error code. Log the code and the timestamp — both are what support needs to trace a request.
Sign-in and access
- The confirmation email did not arrive: check spam, then try signing in — an unconfirmed account can request a new link from the sign-in screen.
- Signed in but nothing is visible: you may be in the wrong organization. Switch with the organization button in the sidebar.
- Buttons are disabled: your role may be viewer. Ask an owner or admin to raise it to member.
Still stuck
Send a message through the contact form with the inspection id, the time it happened and what you expected. You receive a ticket number on screen — quote it in follow-ups.
Was this helpful?
Related guides
- Preparing good product imagesHow to export detail page images so the specification and quality checks pass on the first round.
- Usage and monthly quotaWhat counts as a unit, where to see the remaining balance, and what happens when the quota runs out.
- Issuing and using API keysCreate a key, choose its scopes, call the REST API v1, and revoke a key that leaked.
Did not find the answer?
Send us the question with your inspection id and we will look at the exact job.