Skip to main content

Processing and analysis status

After a session ends, the platform processes the recording and runs any analyses you enabled. This guide explains what happens during that time, how to read the status, and what to do when something fails.

From session end to ready​

When a session finishes, its recording is uploaded and converted before it becomes available for review and export. While this is happening, the participation shows a Processing status; it becomes Ready once conversion and any analyses are complete. If conversion fails, it shows a Pipeline error. See Study participations for the full list of status badges.

Export of a participation is held back until processing finishes, so that an exported bundle is always complete.

Available analyses​

Two analyses run on the server after a session:

  • Speech-to-Text: transcribes the microphone audio. See Speech-to-Text transcription.
  • Eye-tracking (WebGazer): derives fixations and heatmaps from the gaze samples collected during the session. See WebGazer 3.4.0.

You choose which to run in the study's Analysis tab.

Reading analysis status​

Each analysis moves through a simple lifecycle: it is queued, then running, then either completed or failed. The participation list and the Analyses tab show a live badge for each one, and you can watch progress update as it runs.

Processing time depends on the length of the session and how busy the server is. A queued analysis starts as soon as capacity is free, so during busy periods an analysis may wait before it begins. This is normal and does not require any action.

To protect against runaway jobs, each analysis has a maximum running time: transcription stops after 60 minutes and eye-tracking after 120 minutes. An analysis that reaches its limit is marked as failed and can be retried.

When an analysis fails​

If processing is interrupted (for example by a temporary server or network problem), the platform retries the analysis automatically a few times before marking it failed. A failed analysis carries an error indication you can see in the Analyses tab, and a manual retry control.

Common reasons an analysis fails or returns little data:

  • The input was missing or unusable (for example, no recording was available, or no gaze samples were collected).
  • The recording could not be processed within the time limit.

If a retry does not help, check that the session actually captured the data the analysis needs. For eye-tracking, a very low gaze-sample count usually points to poor calibration or interrupted tracking during the session rather than a processing problem.

Cancelling an analysis​

You can cancel an analysis that is queued or running from the Analyses tab. Cancellation takes effect shortly after you request it, and the analysis stops without producing a result. You can run it again later.