Documentation

Troubleshooting

Common errors and what they mean.

update skipped my language

update only adds new strings to files that already exist. If a target file is missing, there is nothing to update. Run translate for that language first, then update from then on.

Some strings were not returned by the provider

The model dropped keys from its response, usually because the response was truncated. ParlanceKit automatically retries the missing keys in a smaller batch. If they still do not come back, the run stops without writing a partial file — re-run to try again. You are not billed for strings that were not returned.

Request exceeds the character limit

Your file exceeds the per-request ceiling for your plan. Split the file, or upgrade. See Limits for the ceiling on each plan.

Too many keys in file

A single file may contain at most 1,000 translatable keys. Split it into smaller files — most frameworks support loading several.

A string exceeded its character limit

A max:N limit is a target, not a guarantee. When the model cannot fit a translation, ParlanceKit reports the string and its length rather than silently truncating it. Loosen the limit, or use approx:N.

My placeholders came back wrong

They should not. Placeholders are masked before translation and restored afterwards, and any string whose placeholders do not survive is retried once, then left untranslated rather than written broken. If you see a corrupted placeholder in an output file, that is a bug — please report it.

Sync says 'already in progress'

Only one sync runs per repository at a time. The response carries the id of the job already running, and the dashboard follows it to completion.

Unknown tone

Tone must be one of the eleven supported values, or a recognised alternative such as casual or polite. Anything else falls back to neutral, and the response tells you so. See Configuration for the list.