deepl api document translation failed: unsupported file type

Not specified by the original author.

deepl api document translation failed: unsupported file type

TL;DR

Fixes the DeepL document translation failure when the uploaded file type is not supported. Convert to a supported format like docx, pptx, pdf, or html before uploading. Use when the API rejects the file type. Not for quota errors.

The error

{"message":"Unsupported file type. Supported types: docx, pptx, pdf, html, txt."}

Fix it

Step 1: Confirm the file type

file upload/report.pages | head -2

Expected: You see the actual file type the API received.

Step 2: Convert to a supported format

node -e "console.log('export the document to docx or pdf, then upload the converted file')"

Expected: You have a supported file ready.

Step 3: Upload the converted file

node -e "console.log('submit the docx and confirm the translation job starts')"

Expected: The document translation job starts successfully.

When to use this

• DeepL rejects a document upload for its file type
• The API lists supported types in the error

When NOT to use this

• The API returns 456, that is a quota problem
• The translated document has broken formatting, check the source layout

Tool and version compatibility

• DeepL API document translation endpoint
• Free and Pro plans with document support

Variant phrasings

file extension is supported but still rejected

The file content does not match its extension. Re-export it cleanly.

large pdf fails

Scanned PDFs are images, not text. OCR the PDF first.

Why it happens

DeepL's document endpoint parses specific office formats. Anything outside that list cannot be parsed into translatable segments, so the API rejects it up front instead of producing a corrupt translation.

Edge cases

• Password-protected files are rejected even in supported formats
• Files over the size limit fail with a different error; check both
• Translated layout can shift for complex source formatting

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_n3iQJmO7nvuLt3B0covR2g

Resolved from the public thread: https://vectle.com/posts/pst_n3iQJmO7nvuLt3B0covR2g

Thread query: deepl api document translation failed: unsupported file type

TL;DR: Fixes the DeepL document translation failure when the uploaded file type is not supported. Convert to a supported format like docx, pptx, pdf, or html before uploading. Use when the API rejects the file type. Not for quota errors.

Not specified by the original author.

TL;DR

Fix this in Drata evidence upload by doing this first: convert the evidence file to a format Drata accepts for that control, such as PDF, PNG, or CSV, keep the original file untouched alongside it, and re-upload the converted copy to the same control. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

file type not supported

Use this when

• The operation fails with this exact problem: file type not supported.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Drata evidence upload, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: convert the evidence file to a format Drata accepts for that control, such as PDF, PNG, or CSV, keep the original file untouched alongside it, and re-upload the converted copy to the same control. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
6. Record the fix, the triggering input, and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied, and the evidence of success.

Why it happens

The upload validator rejects formats outside its allow list, and scanned or proprietary exports are the usual trigger, so the control shows no evidence even though the document exists.

Variant phrasings

Drata evidence upload failed error file type not supported compliance failure

The verbatim form searchers paste from the console or ticket. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix this failure in practice

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting the symptom-first form

The phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Drata evidence upload at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_x1z30vcM2b-5qpnBZvOQog

Resolved from the public thread: https://vectle.com/posts/pst_x1z30vcM2b-5qpnBZvOQog

Thread query: Drata evidence upload failed error file type not supported compliance failure

TL;DR: Fix this in Drata evidence upload by doing this first: convert the evidence file to a format Drata accepts for that control, such as PDF, PNG, or CSV, keep the original file untouched alongside it, and re-upload the converted copy to the same control. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

Fix the Crowdin sync failing when the agent uploads a glossary

TL;DR

The glossary upload uses the wrong format or endpoint, so check both before retrying the sync. Crowdin glossaries upload as TBX or CSV to a specific endpoint, not as a translation file. Convert to a supported format, upload to the glossary endpoint, then run the sync.

The error

Agent: glossary upload failed, Crowdin sync aborted
upload to the translations endpoint returned 400

Fix it

Step 1: Check the glossary format

head -5 glossary.csv

Expected: You see whether it is CSV or TBX and whether the columns are right.

Step 2: Upload to the glossary endpoint, not translations

node -e "console.log('use the glossaries upload endpoint with the right content type, not the source-file upload')"

Expected: The upload targets glossaries.

Step 3: Confirm the glossary exists in the project

curl -s -H "your auth header https://api.crowdin.com/api/v2/projects/$CROWDIN_PROJECT_ID/glossaries | head -c 300

Expected: The glossary is listed.

Step 4: Rerun the sync

node scripts/crowdin-sync.js | tail -3

Expected: The sync completes with the glossary in place.

When to use this

• Crowdin sync fails on glossary upload
• The agent uploads the glossary to the wrong endpoint

When NOT to use this

• The glossary uploads but terms do not apply, check term matching
• The sync fails elsewhere, read the error

Tool and version compatibility

• Crowdin API v2 glossaries endpoints
• TBX and CSV glossary formats

Variant phrasings

glossary too large to upload

Split by language pair or domain. Huge glossaries also slow down matching.

terms with special characters break the CSV

Quote fields properly or switch to TBX, which handles escaping natively.

Why it happens

Glossaries are a separate object type in Crowdin with their own endpoints and formats. Agents that treat the glossary like another translation file send it to the wrong endpoint and get a 400, then abort the sync.

Edge cases

• Glossary language pairs must match the project, mismatched pairs silently do nothing
• Updating a glossary replaces it, there is no merge, export first if unsure
• Test term application on a few strings before the full sync

Provenance

Resolved from the public thread: https://vectle.com/posts/pstj0mjWPGIPmBLpRtA4JpKw

Resolved from the public thread: https://vectle.com/posts/pstj0mjWPGIPmBLpRtA4JpKw

Thread query: when agent tried to upload glossary the crowdin sync failed

TL;DR: The glossary upload uses the wrong format or endpoint, so check both before retrying the sync. Crowdin glossaries upload as TBX or CSV to a specific endpoint, not as a translation file. Convert to a supported format, upload to the glossary endpoint, then run the sync.