Tasks

Data Operations

Data Operations are background bulk actions on a task's data — permanently purging proctoring files, deleting test sessions or candidates, or re-scoring completed sessions against the current test. Only one runs per task at a time, and deletions cannot be undone.

Updated 2026/10/23

Some changes to a task's data are too large, too slow, or too final to happen with a single click in a table: wiping the proctoring files of a finished exam, erasing candidates for a privacy request, or re-scoring hundreds of completed sessions after an answer key was corrected. These run as data operations — they are started from the task, processed in the background item by item, tracked in an Operations list, and leave a record of what they did.

The four operations

OperationWhat it changesCan it be undone?Affects results?
Purge Proctoring MediaDeletes the photo, video, screenshot and screen-recording files only — sessions, answers and results stayNoNo
Delete Test SessionsDeletes each session's entire record: results, answers and answer files, proctoring media, logs, AI evaluationsNoThe sessions disappear from results and analytics
Delete CandidatesDeletes the candidate record, invitations, chat history and reference photo — and every test session the candidate hadNoTheir sessions disappear from results and analytics
Test SynchronizationUpdates completed sessions' questions and/or scoring from the current test, then recalculates their resultsNot automaticallyYes — scores, pass/fail and certificates can change

Where to start an operation

  • For the whole task — open the task and go to the Data Operations tab. The Data deletion tab holds Purge all proctoring media, Delete all test sessions, Delete all candidates and Delete soft-deleted candidates, with counts of what each would affect. The Synchronization tab holds Sync all completed sessions.
  • For selected test sessions — select up to 100 rows in the Test Sessions table and use the bulk actions menu: Purge proctoring media, Sync with test or Delete permanently. A single session can also be deleted from its row menu.
  • For selected candidates — select up to 100 rows in the Candidates table and choose Delete permanently.

Every destructive operation asks you to confirm and to tick an acknowledgement that the data cannot be recovered before it starts.

Who can run them

The organization owner and users with the Manager or Operator role. For everyone else the bulk actions are disabled and the Data Operations tab only shows status.

How an operation runs

  • In the background. Starting an operation returns immediately; the work continues on the server even if you close the page. Large tasks can take a while — progress is shown in the Operations list.
  • One at a time per task. While an operation runs, the task is locked for other data operations: the buttons are disabled and a banner shows what is running. Different tasks are independent.
  • Item by item. Each session or candidate is processed on its own, so one failure doesn't stop the rest — failed items can be retried later.
  • Cancelling stops, it doesn't restore. Cancel operation stops new items from being processed; anything already deleted stays deleted.

Following an operation, retrying what didn't finish, downloading deletion logs and unlocking a stalled task are covered in Tracking & Recovering Operations.

Deletion is permanent — there is no recycle bin, and support cannot bring the data back. Before a deletion, export anything you need to keep (results, reports, recordings). If you only want to stop a session from counting, exclude its result instead; if you only want to free proctoring storage, purge the media and keep the session.
Good to know