Skip to content

Operations & downloads

All long-running work — game version downloads and installations — on one page: progress, cancellation, history.

StatusState
queuedQueued (active)
runningRunning (active)
completedFinished successfully
failedFinished with an error
cancelledLegacy record from older launcher versions

A successful cancellation leaves no history entry. Waxlight:

  1. cancels the operation context and waits for the downloader/installer to stop;
  2. removes both <file>.partial and <file> from the downloads/ directory;
  3. deletes the operation row from the database and emits operation:removed;
  4. releases locks and resolves the cancel call.

If filesystem cleanup fails, the operation is marked failed and the call returns an error — the row is kept intentionally to surface the problem and let you retry deletion after fixing permissions.

Official game packages download to downloads/<name>.partial. After checksum verification the file is renamed without .partial. On a network error the partial file is kept — the next attempt resumes where it stopped when the CDN supports HTTP ranges.

  • Active operations can only be cancelled.
  • Finished ones can be deleted individually (with confirmation) or cleared all at once.
  • Deleting active operations is rejected at the database level: the guard holds even against a misbehaving client.
  • The list is newest-first and limited to 100 records.

Page contract: operations-page.md.