Operations · Recovery

Keep failure visible. Replay the work Omni Loader can recover safely.

Omni Loader records runs, stages, tables, task status, warnings, errors, and failed work payloads. A reported failed task can be cleaned up and replayed from the recovery workflow.

Plan my migration Explore validation

Why this path matters

Keep each migration run inspectable.

The local state store tracks projects, runs, stages, tables, and work status while logs capture summaries, warnings, errors, SQL, and troubleshooting detail.

What changes for you

Retry work that finished with an explicit failure.

Recovery can reconstruct supported failed direct loads, staged streams, comparisons, indexes, and foreign keys, then rerun configured validation.

  • ✓Direct load tasks
  • ✓Remote-storage stream tasks
  • ✓Comparison tasks
  • ✓Index and foreign-key creation

The payoff

See what the capability changes.

Run history

Reviewable execution

Inspect stages, tables, progress, warnings, and errors.

Failed tasks

Serialized replay

Recover supported work after a task reports failure.

Scoped

Target cleanup

Clean the failed table or filter range before selected retries.

Where the work happens

The details that make the result usable.

At a glance

A visual summary of the work.

Illustration of a migration relay and resumable transfer path

Clear boundary

Failed-task recovery is not a distributed durable queue.

A host or power loss before a task records its failure may not leave the serialized payload required for replay. Plan process-level restarts and validation accordingly.

Take the next step

Plan recovery around explicit evidence.

We will identify retryable work, cleanup behavior, validation, and the operational response to a process-level interruption.

Plan my migration