Building an upload plan — Upload & scheduling

On the Upload page:

Pick stacks — one or many, from the Stacks for upload panel.
Pick the schedule — start date and window. The calendar is the date picker: click a day to start the window there.
Run it. A live log shows every post as it's created.

FIG 1Scheduling in the hub: a click on a calendar day moves the upload window, then Start upload opens the pre-flight summary — click to play.

Which stacks are listed

Stacks for upload holds every stack whose content is ready — text, carousel and story stacks need no render. A stack a real run handled leaves the list when that run ends: posted, in the API modes; written into the import file, in the CSV modes. Uploaded · N in the panel head shows them again for a deliberate re-upload, and Add to upload list in a stack's menu puts a single one back.

NOTE

Dry runs and CSV rebuilds never hide a stack — only a real run does.

When each post goes out

The planner spreads the posts over the days of the window, per brand and platform, at most one post per day per brand × platform. Times come from the platform slot table unless the brand has its own: a brand posting time wins, several comma-separated times cycle one per plan day, and Custom times rules pin an exact time per platform and/or post type (a matched rule posts at its time and skips the same-day stagger across platforms).

FIG 2One post per day per brand and platform inside the upload window.

When the batch is bigger than the window

Ten stacks into a five-day window would normally mean every brand drops the same five. Instead, each brand picks its own subset — least-used stacks first — so brands post different material and every stack lands somewhere once enough brands run; a brand keeps one set across all its platforms (crossposts stay crossposts). Batches that fit the window post completely, as before. The pre-flight summary always shows the real planned count.