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

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

Повторный запуск загрузки ассетов приводит к дублированию и блокировке аккаунта. Использование простого журнала (upload_tracker.py) позволяет отслеживать завершённые загрузки и предотвращать дубли.

Задача

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

Результат

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

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

• 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

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

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.

Источник

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.

Источник

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

Источник