Understanding the analysis
Why does my analysis look wrong or fail?
A generated result depends on the text that reached the analysis request and whether the provider returned a usable response. Check the source transcript first, then retry when the session is marked failed. Still stuck? Contact support.
Stuck on Analyzing #
A session left in processing for more than 180 seconds is considered stale and is marked failed when a session read performs the recovery check. This handles a request that ended without saving a final status; it does not mean all analyses finish within 180 seconds.
Once the session is failed, the workspace can offer a retry. Avoid starting repeated requests while a session is still processing. Provider errors, timeouts, invalid model output, network interruption, or request throttling can prevent a result from being saved.
- Provider, timeout, or network errors can prevent saving.
- Invalid model output or throttling can also fail a run.
- Processing turns stale after 180 seconds; a later read marks it failed.
Poor transcript or wrong language #
Review the transcript for missing phrases, names, negation, punctuation, and speaker attribution. Correct text in the editable transcript and save the change before requesting another analysis. Speech recognition uses a language hint; unknown hints fall back to English in the configured Deepgram provider.
The analysis language is a separate setting. Choosing another output language triggers a new analysis rather than translating the current one. Analysis requests use no more than the first 50,000 transcript characters, even when the saved transcript is longer.
-
Check the saved transcript for names, negation, omissions, and speakers.
-
Correct and save the text.
-
If marked failed, retry instead of starting duplicate runs.
-
Compare the new result with its source text.
Missing data is not zero #
'No data' is intentional when a field has no available value or the analysis did not return that item. It should not be read as no risk or a clean result. Some employee score inputs begin empty or with initialized values, so confirm that the source records are maintained.
If a retry also fails, preserve the session ID and note the displayed error for your administrator. Do not repeatedly edit away context just to produce a score.
| Status | What it means | What to do |
|---|---|---|
| draft | Editable session draft. | Finish transcript if ready. |
| transcribed | Transcript saved before analysis. | Review before analysis. |
| processing | Analysis request in progress. | Wait; avoid another request. |
| completed | Analysis result saved. | Review result and source. |
| failed | No usable result saved. | Check the error; retry if offered. |
Use this guidance thoughtfully
This page describes the current product workflow; it is not an HR policy or a promise about every deployment. Before acting on information about an employee, verify the source record, consider context the system cannot see, and use your organization's process. If a control behaves differently from this guide, check the current workspace UI and confirm the saved result rather than assuming an action completed.