Tasks Data Operations

Tracking & Recovering Operations

Every data operation is listed as a run with its items in the Operations list — with live progress, a deletion log per deleted item, and actions to retry what didn't finish, run again, cancel, or unlock a task whose operation stalled.

Updated 2026/10/23

Data operations run in the background and can take a while on large tasks, so the task's Data Operations tab is also where you watch them: what is running now, what each past run did, which items didn't finish, and what to do about them.

While an operation is running

A banner at the top of the tab says which operation is running — for example Deleting all candidates — and the buttons for starting another one are disabled until it finishes. Cancel operation stops it: work that already started is finished, no new items begin, and nothing already deleted, purged or synced is restored.

The Operations list

Every operation started on the task appears as a run, newest first: what it was (Purge proctoring media, Delete test sessions, Delete candidates, Sync test sessions), whether it covered All or Selected items, when it started, and its progress — for example 118 of 120 deleted. Deletion runs also show how many sessions or candidates were skipped because a test session was in progress, and candidate deletions how many test sessions were removed with the candidates.

Open a run to see its items — one per session or candidate — filtered to Unfinished or All. Each item shows its status, and Details breaks a deletion down into its steps and the number of files deleted.

StatusMeaning
RunningBeing processed now
CompletedFinished successfully
FailedGave up after repeated errors — can be retried
CancelledStopped by Cancel operation before finishing — can be retried
StalledNothing has progressed for over 15 minutes — see below

Deletion logs

Every deleted test session and candidate has a Log link on its item: a plain-text file listing each record and file that was removed, one per line, with a header naming the session or candidate, the task, who requested it and when it finished. Keep it when you need proof of an erasure.

Finished items are cleaned up from the list 14 days after they complete — download any log you want to keep before then.

When something didn't finish

  • Retry (on an item) — runs that one session or candidate again, with the same settings its operation started with.
  • Retry N unfinished (on a run) — runs every failed or cancelled item of that run again. Items that already finished are not touched.
  • Run again (on a run) — starts a fresh run over the whole task with the same settings, for when an operation stopped before reaching every item. Sessions or candidates already deleted or purged are simply not found again; a sync re-syncs every completed session.

A retried deletion is rejected again if the session — or one of the candidate's sessions — is now in progress. End the session first.

Stalled operations

TestInvite automatically restarts work that stops unexpectedly. If an operation still makes no progress for over 15 minutes, it is shown as Stalled: it will not finish or release the task on its own. Mark failed & unlock marks every unfinished item as failed and unlocks the task within a few minutes; nothing already processed is undone. You can then use Retry N unfinished to pick up where it stopped.

A run marked Completed doesn't always mean every item was reached — the run's summary says so when it stopped early or left items unfinished, and the button it suggests (Run again or Retry N unfinished) is the right next step.
Good to know

No. Purged media, deleted test sessions and deleted candidates are erased permanently — there is no recycle bin, and TestInvite support cannot restore them. Cancelling an operation only stops it from processing more items. Before deleting, export the results, reports or recordings you need to keep.

Deletions never touch a test session that is in progress, so nobody loses an attempt they are still working on. In a Delete all test sessions or Delete all candidates run, such sessions — or the candidates taking them — are skipped and counted on the run; when selected in a table they are rejected. End the session from the Test Sessions table, then delete again — for a run, Run again picks up everything that remains.

Only one data operation can run on a task at a time, so a task's data is never being purged, deleted and re-scored at the same moment. While one runs, the other buttons and bulk actions are disabled. Wait for it to finish, use Cancel operation, or — if it is shown as Stalled — use Mark failed & unlock. Operations on other tasks are not affected.

No. The credits a test session used are spent when the session runs, and deleting the session — directly or together with its candidate — does not return them.