Live

Schedule releases for a multi-image batch

Admit several artworks and release them now or hold them in the paced batch lane. Hosted Web's server sweeper advances elapsed cadence slots without an active login or open dashboard. On Mac, keep the app running.

Availability
Live
Last verified

What this does

Admit several artworks and release them now or hold them in the paced batch lane. Hosted Web's server sweeper advances elapsed cadence slots without an active login or open dashboard. On Mac, keep the app running.

Before you begin

  • Confirm the store and product line the Drop Zone is aimed at, so the whole batch lands where you want it.
  • Use matching JSON sidecars for per-image copy or routing that must survive a paced hold. The hold path does not carry a batch sheet.

What changes outside ArtDrop

Accepted is the browser label for a nonempty saved list and does not prove processing or an external result. Publish all now moves staged files toward processing. A paced choice holds files until their slots are due. Hosted Web's sweeper releases elapsed slots and records durable worker admission without a dashboard request. Scheduling promises no ranking, traffic, sales, or completion time.

Space a batch out. Choose immediate release or the paced batch lane. Hosted Web's server sweeper advances elapsed cadence slots without an active login or open dashboard. On Mac, keep the app running.
ArtDrop batch scheduling screen asking how fast the artworks should go out, with a per-day rate and Start scheduling.

Steps

  1. Admit the whole set

    Drag, select, or paste several supported artworks. The server holds a multi-image upload until you choose. Closing the choice dialog with Escape or its backdrop selects Publish all now.

  2. Release now or choose the initial pace

    Choose Publish all N now, or Space them out over time. The initial UI choices are 1, 2, 5, or 10 artworks released per day, or about 1 per hour. They count artworks, not provider products.

  3. Let Hosted Web advance the pace

    On Hosted Web, the server sweeper releases every elapsed cadence slot without an active login or open dashboard. It persists worker admission so a temporary launch failure can be retried. On Mac, keep the app running.

  4. Read the persistent card narrowly

    The card reports the held rate-lane count, names, and next release. Its rate selector offers 2, 5, 10, and All at once, so it cannot reliably display an initial 1-per-day or about-1-per-hour choice.

  5. Use Clear Queue to release held work now

    Clear Queue attempts to move every paced and timed file, with matching JSON, into processing. A filesystem failure can leave a partial move, so verify the restored list and remaining schedule. It is not delete or per-target cancel. The card's All at once option moves no held files.

Expected result

On Hosted Web, each elapsed paced slot moves a held artwork toward processing even while signed out with the dashboard closed. On Mac, the app remains running. Every released artwork still needs route-specific external confirmation.

Good to know

  • Hosted Web cadence advances through the server sweeper without an active login or dashboard. Mac cadence still requires the Mac app to remain running.
  • Rate labels mean artworks released: 1, 2, 5, or 10 per day, or about 1 per hour. The endpoint itself accepts any integer.
  • The persistent card's All at once option does not release held work. Use Clear Queue for release-now behavior.
  • Paced batch scheduling and per-store timed releases are separate lanes. Hosted Web sweeps due work in both lanes without an open dashboard. On Mac, the app must remain running. A Mac purchase does not include Hosted Web.
  • Scheduling has no promised marketplace-ranking, traffic, sales, or completion-time benefit.

Troubleshooting

  • Hosted Web paced work did not advance? Check the saved schedule and Live Log, then contact support if due work remains held. Opening the dashboard is not required for normal advancement. On Mac, confirm the app stayed running.
  • Want held files moved now? Use Clear Queue, not the All at once rate option, then verify both the restored list and any schedule entries that remain.

How to undo or clean up

Clear Queue attempts to move every paced and timed file, with matching JSON, into processing. A filesystem failure can leave a partial move, so verify the restored list and remaining schedule. It is not delete or per-target cancel. It does not undo any external record.