Troubleshooting
Fix common AI Glot upload, mapping, credit, progress, download and developer-access problems without losing work.
Open the symptom that matches what you see. The fixes below do not delete a translation or consume additional credits.
The CSV is rejected before upload
Re-export it as UTF-8 CSV and check for blank or duplicate headers, unclosed quotes and rows with a different number of columns. Upload ceilings are per format: 60 MB for CSV, 4 MB for a locale file. See Files and formats.
A cell is too long to translate
Each individual source cell selected for translation may contain up to 50,000 Unicode characters. Split longer HTML or editorial content into multiple rows or smaller fields, then upload the revised CSV. This limit applies to one cell and is separate from the smaller limit used to group ordinary cells into translation tasks.
The plan covers the wrong columns or languages
The plan is a proposal. Say what to change in plain words, such as “only the description column” or “leave the SKU column alone”, and check the item table to see exactly which values will be sent. Nothing is charged until you approve.
The credit estimate looks too high
The cost is the measured word count of what the plan will translate. Open the item table to see which values it includes, and refine the instruction to leave out IDs, URLs or metadata you do not need. Translating into several languages multiplies the source count by the number of destinations. Paid plans can use Lite for eligible bulk content at about one third of Standard cost.
Translation appears slow
Keep the batch page open to see its live phase and percentage, but the job continues if you leave. Multiple destination languages, many short cells and retries can take longer than a similarly sized file with one destination. AI Glot emails you on completion.
If progress has not changed for an extended period, reload once. The server, not the browser animation, is authoritative. A terminal failure returns reserved credits automatically and shows a safe error message.
The downloaded file will not import
Compare it with the original export: same delimiter, headers, number of columns and row identifiers. AI Glot preserves these, but the destination system may impose its own required fields, value lengths or locale codes.
API, CLI or MCP authentication fails
Check that the credential is active, belongs to the expected workspace and has the required scope. For CLI problems, run aiglot doctor. For structured API failures, follow the docs_url and quote the returned request_id when contacting support.
A tool will not start a translation
Check the scope, not the tool: the REST API, the MCP tools and the CLI can all start one. Creating and approving both require batches:create. A member’s connection also needs that scope inside the workspace’s member ceiling: new workspaces include it, but workspaces created before 31 August 2026 may not, so an admin may have to tick it in the Permissions tab of Developer tools. Approving without planning first fails with no_plan_yet.
Contact support
If the steps above do not resolve the issue, open Support in the app. Include the workspace name, batch ID and request ID where relevant, but never include an API key or access token.
Live chat opens a chat bubble in the corner of the page, and Email support writes to the address shown. Replies typically arrive within one business day.