Batch hundreds of .vsd into PPTX: manifests and per-row reruns beat “the folder looks full”
`batch-vsd-pptx` serves inventory sweeps, compliance archives, and multi-product deck factories. Silent per-file failures, clobbered outputs, or inability to rerun one bad row force expensive full rewashes. Freeze manifests with source path, page span, slide size, object key, status, slide count, hash, and duration; throttle giant pages. Nightly reconcile success rows vs object counts—gaps close under tickets before the next batch.
Batch playbook: golden and corrupt pilots pin engine versions, then checkpoint manifests for resume and failure compensation
- Sample the nastiest, oldest, and a few corrupt .vsd files to validate defaults; data owners sign manifest schemas—no ad-hoc CSV headers per team that break reconcilers.
- Persist manifest slices every N rows with failure lists; encode repo and path hashes in output keys; randomly open decks to macro-check slide counts are not zero or suspiciously tiny—halt on systematic drift.
- Archive manifest hashes plus read-only bucket snapshots; when rerunning failures, skip legally approved customer-facing rows unless a forcing ticket exists.
VSD to PPTX (batch) FAQ: manifests, resume, collisions, empty-deck detection, compliance seals
Logs say success but object counts lag sources—which manifest columns first?
Inspect row status, skip reasons, and empty output URIs—usual culprits are path encoding, locks, or human deletes mid-run, not random engine noise.
Parallel CI jobs write one prefix—what build context must manifests capture for forensics?
Record pipeline id, commit SHA, image digest, source checksums, and artifact hashes; forbid an unversioned latest prefix as sole truth.
Some outputs are suspiciously small—automate empty-deck detection how?
Enforce minimum slide-count thresholds and first-slide render hashes; flag suspect_empty and open manually in PowerPoint to see white decks vs render faults.
Duplicate basenames across folders collide when flattened—how to encode directories?
Prefix outputs with path hashes or repo names in manifests; never flatten to single-level filenames across trees.
Regulators want a point-in-time snapshot—is CSV alone enough?
No—seal bucket versions or read-only snapshots and hash the manifest file; spreadsheets alone are mutable and fail non-repudiation.