Guardrails for unattended posting
Manual posting always behaves as described in Upload & scheduling: warnings, then your confirmation. Unattended contexts — schedules, the watch folder and agent integrations — run under stricter defaults:
- Uploads are dry-run by default: the run shows exactly what would post.
- A real post needs an explicit approval — in the job, in the schedule, or per post in the review queue.
- Approved runs still respect per-account rate limits (skipped posts are logged; the batch continues) — and the limit ledger counts every real post from every part of the app, so an automated run can't pile on top of a manual batch unnoticed.
- Exact duplicates are skipped. A post whose file and texts this stack, brand and platform already published is dropped and reported, unless the caller deliberately allows duplicates.
- Posting is asynchronous. An assistant's upload run returns a run id and keeps going in the background; asking again for its status is right, starting it a second time is not — the second call answers "already running".
WARNING
Approval given once is not approval for every night. A schedule's Real run flag and a job file's own approval do not by themselves post through the Zernio or Metricool API modes — nobody is watching a 09:00 run. Those runs post what the review queue approved and skip the rest. The two CSV modes honour the flag on its own: their output is a file you import by hand.