Skip to main content
Version: v5.5.0

Maintenance

Settings → Admin → Maintenance (Settings → Maintenance in the desktop app) shows whether the instance is healthy and runs its background cleanup.

System check​

The system check tests the instance from both the server and your browser:

CheckWhat it confirms
Compute workerThe app can reach the worker.
Object storageThe storage bucket is reachable.
Playback secretA playback signing secret is available.
ProvidersAt least one shared TTS provider is enabled.
Address you openedThe address in your browser matches BASE_URL.
Playback audio URLYour browser can reach the worker's playback address, and it is not blocked as mixed content.

Each row reads OK, Check or Fix. Rows that are not OK say what is wrong and which setting fixes it. Choose Run again after changing configuration.

The desktop app adds Open logs folder here.

Scheduled tasks​

TaskDefault intervalWhat it does
Clean up unowned documents6 hoursRemoves document files and generated artifacts that no longer have an owner.
Clean up expired files1 hourRemoves uploads that were never finished and DOCX conversions after a day, and account export ZIPs after seven days. Audiobooks are kept until their audio is cleared.
Clean up compute history1 dayReleases expired compute leases and removes old limit counters and events.
Repair storage usage1 dayBackfills audio usage for existing users, then repairs users active in the last seven days. The worker scans audio; pages read the stored SQL totals.
Finish pending deletions15 minutesFinishes account deletions interrupted by a restart or failed cleanup, then deletes audio and exports left by deleted documents and accounts, including the second pass after an account is deleted. On Vercel it runs with the daily cron.
Delete idle guest accounts1 dayOff by default. Deletes guests whose account and sessions have been idle for the Guest idle period (90 days by default, under Guest sessions), and resumes previously requested deletions.

After v5.4.1, Clean up expired files also covers account exports (formerly Clean up expired exports) and Finish pending deletions also covers account deletions (formerly Finish pending account deletions). Each keeps its own earlier on/off setting, so if you had turned off the uploads or storage-retry task, turn it back on to keep the merged work running.

You can turn each task on or off, change its interval, or run it now. Storage cleanup and account deletion run as durable jobs on the compute worker. The panel shows live progress and the final result, including failed items. You can leave the page while a job continues; opening Maintenance again reconnects to its progress. Compute-history cleanup stays in the app because it only changes the application database.

The web request only queues a job. The worker performs storage scans and deletes, and makes short authenticated calls to the app for database ownership checks and row cleanup. A web request ending or a progress stream reconnecting does not cancel the job.

Waiting behind another maintenance sweep does not expire a queued cleanup. The panel refreshes its task list to discover scheduled runs; detailed cleanup progress uses SSE. Last-run times and durations reflect worker completion, even when the app learns about completion later.

Account deletion first revokes sessions and displays Deletion pending in Users. The account and its ownership rows are removed after storage cleanup succeeds. Failed deletions retain that marker and are retried by Finish pending deletions. Selecting multiple users queues one cleanup job for the selection. Deleting your own account from Settings → Account, and the guest left behind when a guest signs up or signs in, go through the same job.

Only one copy of a task runs at a time, even with several app instances.

How tasks are triggered​

  • Self-hosted and desktop: the app checks for due tasks every minute.
  • Vercel: there is no long-running server, so Vercel Cron calls /api/admin/tasks/tick. Set CRON_SECRET; requests without it are rejected. The included schedule runs once a day (the most Vercel Hobby allows), so intervals shorter than a day are not offered there.

Vercel intervals are anchored to the UTC day of the run. A job finishing after the cron request or being reconciled the following day does not postpone the next daily run.