Skip to content

Inspect background jobs and audit activity

Use job status to find why a requested operation has not finished. Use Activity to see recorded Support changes.

Inspect a job

  1. Open Customer Support > Operations > Jobs.
  2. Find the relevant preparation or import/export job.
  3. Read its type, state, attempts and last error.
  4. Fix the cause before using Retry on a failed job.
  5. Refresh the view and check the destination article or export result.

Freshdesk runs have their own history under Operations > Imports. Use that surface for Freshdesk retries, owner changes, conflicts and reversal.

Common causes

An unavailable AI service can block preparation or evaluation. A scanner failure can leave a file under review. Storage capacity can stop a new object write. Lost membership, permission or license can stop work that was valid when it was queued.

A quarantined file must not be treated as clean. An uncertain customer action needs reconciliation, not a generic job retry.

Read activity

Open Configuration > Support AI > Activity. The recent list records actor, time, action and target for Support audit events. It is a bounded recent view, not an unrestricted permanent transcript archive.

Check the result

Verify the actual resource state after a retry. A job being queued or started is not proof that its business operation completed. When reporting a problem, include the job or run ID, time, visible error and expected result. Leave credentials and private conversation text out of ordinary diagnostic messages.