Recording analysis does not start
Identify whether analysis is disabled, waiting, suspended or failing before requesting another attempt.
Recognize the symptom
A recording has no new AI result, remains in the backlog or is shown as suspended. Note whether a manual request works while scheduled analysis does not. These paths can expose different configuration, permissions or command-line PHP problems.
Possible causes
Analysis requires an active license, configured application database, Gemini key and model, and the recording path. Automatic processing also depends on its actual schedule and worker state. An unavailable audio file, provider rejection or suspended item can prevent completion even with populated settings.
Check before changing anything
Open System and utilities and review Gemini settings, background processing and automatic analysis status. Read the recorded reason for the affected file. Confirm the audio exists and distinguish a size or format issue from authentication, quota or provider errors before changing the model.
Take a targeted action
Correct the specific dependency and use Requeue for selected suspended recordings when another attempt is justified. An update deliberately preserves suspension; it is not a retry mechanism. Avoid repeatedly submitting a large backlog while the provider or audio source is still unavailable.
Verify the result
Follow one representative recording from waiting through completion and open its actual result. Check the scheduled path separately if that was the failure. A readiness result checks local prerequisites, not a successful Gemini request; retain the sanitized provider error if a configured request still fails.