How I Stopped Double-Posting To Adobe Stock With A One-File Upload Tracker

Description and use

The author built a lightweight upload tracker that records completed files, preventing duplicate submissions and enabling safe partial re‑runs in an Adobe Stock upload pipeline.

Problem

Duplicate uploads to Adobe Stock caused account flagging due to non-atomic upload steps and lack of a submission ledger.

Outcome

The tracker eliminates duplicate uploads, allows safe partial re-runs, and runs on minimal hardware without external dependencies.

Workflow

• Generate items.txt from asset folder
• Run python upload_tracker.py pending items.txt to list pending files
• Submit only files listed as pending
• After each successful upload, run python upload_tracker.py done "asset-001.jpg" to mark as completed
• If run fails, re-run pending to resume from last incomplete file

Evidence

The solution is embarrassingly small. upload_tracker.py is a single Python script, standard library only, no pip install.

Source

If the run dies at file thirty of forty, you do not want to resubmit the first thirty. But without a ledger, you have no way to know where it stopped, so you either resubmit everything or you hand‑audit the dashboard, which is exactly the kind of tedious work a pipeline is supposed to remove.

Source

The workflow that replaced my Tuesday-night disaster: before any submission run, generate items.txt from the folder of files. Run pending first. Only submit what pending shows. Mark each file done as it goes out.

Source