Repair Export Snapshot Drift

The problem

Large data exports often drift when source records change during generation. This leads to missing rows, duplicates in resumed jobs, and reports where totals don't match the exported records.

What it does

• Detects and repairs mixed snapshots and unstable pagination in long-running export workflows.
• Establishes deterministic export contracts using stable snapshot boundaries and immutable ordering.
• Implements resumable checkpoints and idempotent retries to handle worker crashes without data corruption.
• Enforces atomic file finalization to prevent partial or corrupted downloads from being exposed to users.
• Verifies integrity through row count, checksum, and aggregate total validation.

Frameworks & tools

Works with any database (SQL/NoSQL), ORM, or queue system. Supports CSV, XLSX, JSONL, and multi-file archives. Compatible with object storage providers like S3 for multipart uploads.

Why this beats prompting it yourself

Hand-writing consistent export logic requires complex handling of database transaction limits and race conditions. This skill provides a rigorous 17-step verification process that covers edge cases like concurrent mutations and cross-tenant isolation that simple prompts miss.

Use cases

• Repairing financial reports where totals must match a frozen point-in-time snapshot.
• Fixing broken CSV exports that skip records due to offset drift.
• Implementing safe resume logic for multi-gigabyte exports that frequently time out.
• Ensuring legal and audit logs remain immutable and complete across distributed workers.

Known limitations

Does not automatically apply migrations to production. Database-specific snapshot limitations (like MVCC retention) must be reviewed for extremely long-running jobs.