Translate, cancel and resume

Objective: Start processing, monitor its state and understand when a session can resume.

Applies to: An eligible project with configured languages/provider and selected content. Resuming depends on valid cache, stage, project identity and retention. Plus cache for multiple projects does not mean simultaneous translations.

Before starting: Check network, credentials, service quota and available space. If you want review before application, check that the corresponding option is enabled for the current package and state.

Steps

1. Check the project, target language, provider and scope.
2. Start or continue processing from the current stage.
3. Monitor stages and messages. Extraction, translation and output preparation are distinct; a stage percentage does not establish that game files have changed.
4. To interrupt, use Cancel and wait for acknowledgement. An ongoing network request may not stop immediately.
5. To resume, return to the same project and check whether continuation is offered. Deleting cache or replacing project files can lose the previous point.
6. If the app asks about another project’s cache, read the condition before clearing/replacing it. Free/Basic can require resolving the previous session.
7. Continue only if the session matches the intended project and configuration. Invalid or missing sessions may require new processing.
8. At completion, follow the displayed state. If review is available, review and apply. If application already occurred automatically, test the result instead of applying a second time to imitate this guide.

Expected result: Processing completes or cancellation is acknowledged, with a clear next state. Resuming does not guarantee fewer provider calls in every case.

If it fails: Record the stage and message. Check provider and quota before retrying. Expired, deleted or incompatible cache can prevent resuming. Do not change integrity files or disable validation.