Administration & Recovery
Inspect durable processing failures, retry eligible bookmark work safely, and preserve the history needed to diagnose recurring problems.
Arivu keeps administration separate from ordinary personal knowledge work. Administrators can manage users, runtime settings, API usage, system status, audit history, and processing recovery without exposing those controls to non-admin users.
Inspect Processing Failures
Open Administration, then API Usage to see durable failed jobs and failed summaries. Entries can include the owner, bookmark, attempt count, timestamps, provider and model context, safe error codes, and recorded failure details.
The two lists answer different questions:
- Failed jobs show durable bookmark-processing jobs in a failed state.
- Failed summaries show summary validation or evidence failures, including cases that did not exhaust the surrounding job.
Use the bookmark link to inspect the retained reader and capture state before retrying. Arivu keeps the bookmark and its last good evidence available when a refresh fails.
Retry Eligible Work
An administrator can retry one eligible failed bookmark-processing job, select several failures, or retry the most recent failed processing attempt per bookmark for a specific user. A retry creates new queued work rather than rewriting the failed record.
Arivu rejects work that is not safe to retry from Administration and prevents a duplicate active retry for the same bookmark. Bulk results report how many jobs were queued and how many were skipped, so partial recovery remains visible.
Keep the Audit Trail
Retrying leaves the original failed job in history. An audit event on that failed job records the new job ID and the administrative action. This makes repeated failures diagnosable without turning the recovery control into a history-clearing button.
Before broad recovery, confirm that the underlying provider, capture runtime, storage, or network issue is resolved. Prefer a small selected retry first, then use the per-user action when the result is healthy.
For host-level status, upgrades, and backup recovery, see Self-Hosting Arivu. For evidence selection and safe capture fallback, see Preservation and Sharing.