Conversion Stuck? Read the Stage Before Retrying
Understand queued, processing and finalizing states, multi-pass progress, cancellation and safe retries.
Updated · Cyber Search MatchRead the stage and task details before submitting another job. Queued is waiting, a new encoding or loudness pass can change progress, and Finalizing is still working until the output has been written and checked.
Match the state to the next action.
Keep the tab open during upload. Once the task has been accepted into the queue, processing runs in the background and you can return through My conversions. A slow queue is not evidence that uploading the same file again will help.
The converter reads process progress rather than advancing a timer. Duration, elapsed time and speed are useful clues, but not every stage produces a steady speed or reliable remaining-time estimate.
| Stage | What to do |
|---|---|
| Uploading / Inspecting | Finish the transfer; read any source error. |
| Queued | Wait for a compatible worker; avoid duplicates. |
| Processing | Check the current pass and task details. |
| Finalizing | Wait for file writing and output checks. |
| Failed / Cancelled | Read the reason before retrying. |
Allow for more than one processing pass.
Two-pass encoding first gathers information and then writes the result. Perceived loudness normalization also measures the signal before its rendering pass. A percentage or processed range that starts a new pass is not a promise that the whole job has restarted incorrectly.
Finalizing can include container writing and result inspection. The interface only reports 100% after the result is complete and verified. A fast encode followed by a slower finalization is possible, especially for larger files.
Cancel or retry deliberately.
Use Cancel conversion when the submitted settings are wrong. Cancelling means the worker is stopping its child processes; wait for Cancelled before starting a replacement. Avoid deleting a task merely to interrupt an upload or processing process.
A worker restart can cause an ordinary conversion to run again from the beginning. Worker leases prevent two workers from executing the same task concurrently, and temporary failures have bounded retries. Arbitrary resume from any timestamp is not promised.
Collect a useful problem report.
Open My conversions and record the task reference, visible stage/error, selected output and approximate submission time. If available, include the processed duration and pass. Do not post private source recordings publicly as a troubleshooting step.
Files have a retention period, shown on completed tasks. A missing expired file is different from a task still processing. For unexplained persistent waits or storage errors, contact support instead of repeatedly resubmitting unchanged settings.
Before you finish
- The latest task state was checked in My conversions.
- There is no duplicate queued submission.
- Any retry follows a visible failure or a deliberate cancellation.
Questions about this workflow
Will closing the tab stop a queued conversion?
No. Submitted jobs run on the server. Closing during upload can interrupt the transfer, so wait until submission has finished.