How Upload_Tracker.Py Stops Double-Posting When You Re-Run A Batch

Описание и применение

Скрипт upload_tracker.py использует простую текстовую книгу для отслеживания успешно загруженных файлов, предотвращая дублирование при повторном запуске пакета.

Задача

Re-running an upload batch can create duplicate submissions, risking account flagging on platforms like Adobe Stock, Vecteezy, and Dreamstime.

Результат

The ledger‑based approach eliminates duplicate uploads, allowing safe re‑execution of batches after crashes or interruptions. The author reports no double‑posts since implementing the tracker.

Рабочий процесс

• Generate output files into the output/ folder
• Build CSV metadata files for each platform with make_metadata.py
• Run python upload_tracker.py pending items.txt to list assets still pending
• Upload each pending asset manually via the platform’s web interface
• After each successful upload, run python upload_tracker.py done "asset-001.jpg" to mark it as completed
• Re‑run the entire process at any time; pending will be empty if all assets are done

Доказательства

The script is a plain-text ledger. Three commands: python upload_tracker.py pending items.txt # shows what is NOT done yet python upload_tracker.py done "asset-001.jpg" python upload_tracker.py status

Источник

The ledger is written after the upload succeeds, not before. If the process dies mid-upload, the asset is still "pending" on the next run, and the re-run picks it up.

Источник

I reconnected, re-ran the batch script from the top, and went to make coffee. When I came back I had 14 duplicate submissions sitting in my Adobe contributor queue.

Источник