Jobs

Jobs is where you check on the scheduled and background work Scryer runs — and trigger it manually when you need to.

• To access: System → Jobs
• To view: Requires manageSystemSettings app permission; direct links also accept manageCatalogSettings

Working In Jobs

If a library scan, metadata refresh, or plugin catalog update seems stuck or never ran, find the job here and check its last-run status before assuming the operation failed or needs to be triggered manually.

If you need to trigger a scan or refresh immediately, run it from here instead of waiting for the scheduled interval.

• Review job names, status, timing, and last-run details.
• Trigger supported jobs manually where the UI exposes that action.
• Retry or inspect failed jobs when supported.
• Compare job output with Activity History and System Overview.
• Use job timing and status to tell the difference between a slow task, a failed task, and a task that never started.
• Run a focused library scan after moving managed files.
• Refresh a plugin or provider catalog after installing updates.
• Inspect a failed cleanup or metadata job before changing settings.
• Confirm the related Activity or title state after a job finishes to verify the intended effect.

Related Concepts

• System Overview — instance health dashboard; check alongside jobs to distinguish health issues from slow tasks
• Activity History — durable log of completed operations; compare with job timing to confirm a job produced its intended effect
• Plugins — plugin catalog refresh is a background job visible and triggerable from this page
• Library Layout — path layout that library scan jobs operate against; confirm roots are correct before triggering manual scans