Safety model, in one paragraph — Upload & scheduling — VidVertex Docs
Docs/Upload & scheduling/Safety model, in one paragraph

Safety model, in one paragraph

Everything user-facing warns instead of blocking: duplicates, limits, re-runs. The actual posting happens on the scheduling platform — VidVertex's job is to make what's about to happen visible before it happens, and to keep a complete record after. Automated contexts (assembly schedules, the watch folder, agent integrations) run under stricter guardrails — dry-run by default, a review queue for proposed posts, rate limits — described in Automation.

FACT

Nothing in the manual flow is ever hard-blocked. Duplicate warnings, platform limits and a posting time already in the past all stop at a warning and leave the decision with you — the button then reads Upload anyway.

RELATED · UPLOAD & SCHEDULING
The assembly line as a loop from the inbox to the schedule and backnewestinbox clipstack fromthe presetcaptions, hooks,textsrenderscheduleone preset,on a timerthe loop closes on the next inbox clipDOCS · AUTOMATIONGuardrails for unattended postingManual posting always behaves as described in Upload & scheduling: warnings, then your confirmation.Google Drive as the transfer vehicle: Metricool re-hosts the file and the Drive copy is deletedVidVertexDriveMetricoolre-hostspostshare linkthe Drive copy is deleted —Metricool has its ownDOCS · GOOGLE DRIVE SETUPWhy this is a one-time choreGoogle only lets desktop apps talk to Drive through an OAuth client that the account owner creates — there is no shared VidVertex key you could paste.The upload window on the calendar: one post per day per brand and platformMTWTFSSupload window · 7 daysone post per day per brand and platform; the calendar is the date pickerDOCS · UPLOAD & SCHEDULINGPost types beyond videoWhich post types reach which platform through the upload plan