Skip to content

Tasks & Logs ​

Tasks and logs are used to track background jobs such as scanning, scraping, and cleanup, with status and execution details.

Purpose ​

  • Observe task state and execution result in one place.
  • Locate failed tasks and inspect error context quickly.
  • Trace scan/scrape history via log entries.

Entry Paths ​

  • Web: System Tools -> Tasks / Library Logs.
  • H5: Storage Management card -> Tasks / Library Logs.

Core Flow ​

  • Task list: inspect All / Running / Completed / Failed statuses and statistics.
  • Task types: source scan, metadata scraping, cleanup, AI categorization, and per-book subtitle transcription. Global transcription cards and service setup live in Subtitle Management.
  • Failure triage: open failed entries and review root cause and retry hints.
  • Log inspection: check scan/scrape event logs in Library Logs.
  • AI categorization jobs expose processed count, remaining count, and failed entries; state is restored after refresh.

Notes ​

  • Only admins can access tasks and logs.
  • If backend services are unavailable, task state cannot be generated or updated.