Control document processing

Read the processing details

Open the document or its Operations entry. Check its stage, processing node, generation model, embedding model, and latest result.

Copying, verifying, loading, tokenising, waiting for capacity, generating, and embedding describe different work. A completed model call does not mean the whole document is complete.

Stop, assign, and resume

1. Select the intended document job and review its current owner.
2. Choose Stop and enter the required reason.
3. Wait for the state to become Paused. Stop requested is not yet a safe handover.
4. Choose Assign and inspect the destinations and their eligibility explanations.
5. Select an approved ready node with the required models and storage access.
6. Review processing settings if needed, then choose Resume.
7. Confirm the new attempt and destination in its processing details.

Check the result

The source document remains available after a stop. Some stages may restart or reuse saved results. Do not assume every interrupted job resumes from the exact displayed percentage.

A stopped worker must finish cancellation and acknowledge it before active work can move. An unreachable owner or expired lease does not make forced reassignment safe.

Understand GPU evidence

Saved policy, selected accelerator, and observed execution are different. Check the actual backend and fallback reason. A GPU preference or reserved slot does not prove GPU execution.

If work appears stuck

Read the original failure and recent section results. Check the owner heartbeat, storage phase, model capacity, and node connection. Preserve the job and request IDs before another attempt.

Do not keep restarting a service or forcing an assignment while writes may still be active.

Next step

Read Manage model capacity and Fix model and upload problems.