Does retry start over? Existing text, transcribedFrames and pending state

retry queues preserved fields; it does not automatically clear and re-recognize everything

Note retry sets the supplied note pending, clears failure and saves without clearing transcript/transcribedFrames there. Transcription opens audio at the recorded frame position and joins later results. Loading leftover recording/transcribing can also mark pending. State reset proves neither complete recovery nor word accuracy, and does not start a new recording.

Different from recapture, mapping and joining

Recapture assesses missing capture, mapping relates material, joining checks boundaries. Here what retry retains and where processing resumes matters. No actual retry, frame edit, model run or restore occurs.

Check Verified scope Manual review Not established
Retry Set pending/clear failure Retained original fields All text cleared/new capture
Existing text transcript retained Earlier versus appended output Everything generated by this retry
Checkpoint Read from transcribedFrames Recorded position versus audio Word alignment/integrity accepted
Reloaded status recording/transcribing becomes pending Queue versus successful processing All crash buffers restored
Worker Pending work with canTranscribe checks Foreground/busy/result Instant/background completion
Empty transcript branch Can advance without adding words Actual speech still reviewed No missing business contents
Save/failure Actual errors/persistence separately Memory/disk/version scope Lossless/permanent restore SLA
Reservation retry does not clear handOffAttempted here Prior attempts/authority New transcription authorizes replay

Synthetic checkpoint note

A failed sample has old text A and position N. Retry queues pending; later work resumes at recorded N. Do not call A new output or pending successful recovery.

Audio, latest persistence and supplied object still need correspondence evidence. Do not edit transcribedFrames to hide gaps. New capture needs a new version; reservations/uncertainty survive retry.

FAQ

Does retry always start at zero?

This method clears neither text nor position; processing resumes from recorded frames.

Does pending prove recovery?

No. It is queued state, not actual file/model/access acceptance.

Is old text all new output?

No. Separate existing transcript from later pieces.

Does advancing an empty piece prove no business speech?

Not independently. Original audio/meaning need review.

Does retry clear handoff reservations?

Not through this method; it grants no resend authority.

Was retry/inference performed?

No. Source review only, without lossless restore/cloud resume/new capture services.

Reading and source

Recapture decision · Material mapping · Segment joining · One handoff · Start · Privacy

Retry/load/worker/transcribe · Checkpoint/reservation fields