Why Running Your Asset Batch Twice Gets You Flagged, and the Script That Prevents It

Description and use

Re‑running an asset upload batch creates duplicates and triggers a review hold. A simple ledger script (upload_tracker.py) tracks completed uploads, preventing duplicates and eliminating the hold.

Problem

Re‑running an asset upload batch creates duplicate submissions that trigger review holds on stock platforms.

Outcome

The ledger script prevented duplicate uploads, removed the review hold, and reduced rejections to normal levels.

Workflow

• Run upload script over asset folder
• Upload each file and wait for platform acceptance
• Immediately mark file as done in ledger via upload_tracker.py done "asset-001.jpg"
• On next run, use upload_tracker.py pending items.txt to get list of unfinished files
• Upload only pending files
• Check ledger status with upload_tracker.py status

Evidence

By noon I had 120 duplicate submissions sitting in a contributor queue, and within a week I had a review hold on my Adobe Stock account.

Source

The upload step only ever consumes the output of pending. If a run dies halfway, the ledger knows which 37 of the 60 finished, and the next run picks up the last 23.

Source

One habit that made this stick: mark done immediately after the platform accepts the file, not after the whole batch finishes.

Source