Skip to content

Storage logs and scheduled jobs

Everything Sliick Files does to a file is logged, and two background jobs keep the org and the storage tidy. This page tells you where to look and what to check.

Every file operation is written to a Storage Log record: the operation, whether it succeeded, the file, any error message, and the timestamp.

The easiest way to read recent activity is the Diagnostics tab in the Sliick Admin app, which shows the last 50 entries. See The Diagnostics tab.

For anything older or more specific, go to Setup → Object Manager → Storage Log → List Views and build a list view.

Log entries older than 30 days are deleted automatically. If you need a longer record, export before they age out.

Storage Log is a private object. Only users with the Sliick Files Admin permission set can read it; Sliick Files User does not grant access.

Sliick Files schedules its background jobs automatically at install. To confirm they are running, go to Setup → Scheduled Jobs and look for OrphanFileCleanupScheduler.

That job runs daily and does two things:

  • Removes leftover file pointer records that no longer point at anything, for example after you disconnect a provider.
  • Sweeps storage debris on Amazon S3, Google Cloud Storage and Azure Blob Storage, removing only unreferenced objects Sliick itself created, never customer files or live thumbnails, and only once they are at least 24 hours old.

A second job purges storage log entries older than 30 days.

If the cleanup job is missing from Setup → Scheduled Jobs, contact Sliick support before scheduling anything by hand.