FAQ

Why is the Resume button missing on my Sync, Export, or Materialize Run?

By design. Sync, Export, and Materialize cannot pick up from where they stopped: each one operates on units of work that have to be re-applied in full to remain consistent. Aborted or failed Runs of these operations expose Rerun instead, which starts the operation from scratch. Profile, Scan, and Promote do support Resume because they track per-container progress and can continue processing only what was left.

What happens to partial results when a Run is Aborted?

Partial results are preserved. Anomalies already written, containers already profiled, computed data already materialized, and any other work the Run completed before the abort remain in the system. The Run lands on Aborted with summary metrics reflecting only what was finished. Resume (where supported) continues with the unprocessed containers; Rerun starts the operation over from scratch.

What is the "Warning: Completed with logs" indicator next to a Run ID?

It is not a separate status. The badge stays Success (green) and the Run is treated as a terminal Success everywhere it counts (Auto-Resolve, summary metrics, downstream consumers). The icon next to the Run ID only signals that the worker recorded log entries during the Run, usually because individual containers raised warnings or partial issues. Open the operation log from the expanded Run to review the entries before relying on the result.

Can I delete a Run while it is Running or Queued?

No. The Delete button is only available after the Run reaches a terminal state (Success, Failure, or Aborted). To stop an in-progress Run, use Abort; once it lands on Aborted, Delete becomes available.

Does deleting a Run also remove the anomalies it created?

No. Delete only removes the Run's own record from the Activity list. Anomalies, computed data, materialized rows, and any other downstream artifacts produced by the Run are kept and remain accessible from their respective pages.

Why can External Scan only be Aborted?

External Scan records the result of a scan executed outside Qualytics (for example, from a CLI step in your own pipeline). Because the actual work happened outside the platform, there is nothing to Resume or Rerun from Qualytics's side. You can still Abort an External Scan that has not finished registering, and Delete it once it lands on a terminal state.

What permission do I need to take actions on a Run?

The Editor team permission on the target datastore lets a user Abort, Resume, Rerun, and Delete any Run against that datastore. Viewer, Reporter, and Drafter cannot act on Runs. Admin user role bypasses team-permission checks.

Where do I see logs for a failed Run?

The operation log is reachable from the expanded Run row. Run-level errors (setup, scheduling, worker-level failures) live in the Run-level log; per-container errors live alongside each container row inside the expanded Run.