Diagnose a translation failure

Before retrying

Keep a copy of the game and the exact error. Identify the application version, engine, workflow stage and recent changes. These checks collect evidence; they do not establish a single cause.

Game not recognized

1. Check that you selected the executable and the complete game structure.
2. Check compatibility information and your account access to the engine.
3. If the expected structure is still rejected, collect the error and version before contacting support.

Provider failure

1. Check the language pair, credentials, network and service quota.
2. Use the test offered by the application and read its response.
3. Avoid blindly repeating batches: calls can consume external quota.

Translation missing in the game

1. Check that application finished and that the text was included in the selected content.
2. Compare one extracted text with its location in the game.
3. Check runtime and license messages. MV/MZ Free Runtime requires LRPGM running and an online account.

Integrity error or unavailable resume

Preserve files and the message. Check whether the project or package changed. Do not remove validation or alter signed payloads. Removed, expired or incompatible cache can prevent resuming; check the session before starting another batch.

Missing image or audio

Check whether the original file exists and its name and path match. Name corrections do not restore the contents of a missing file.

Reporting an issue

Use contact with the version, engine, stage, message and recent changes. Remove credentials, tokens, personal names and private paths from screenshots. Share only examples you have permission to provide. This guide does not promise a support response time.