The calendar and upload history
The calendar
The Calendar page shows the month per brand and platform: scheduled and already-published posts, each with the status its source reports — including the ones that failed. Where they come from follows the upload mode, and a badge on the panel names it: Metricool's planner in the Metricool API mode (times as the planner shows them), your Zernio account whenever a Zernio key is configured, and the newest CSV export as a fallback when neither can answer. Days with real posts draw solid; the projected upload window draws as a dashed outline. Clicking a day moves the upload start date there; a day with posts opens its list, and a post that can be traced back to its stack opens that stack in the editor.
Upload history
Every upload attempt is logged per stack: file, brand, platform, timestamp, mode, result, post reference. That log powers duplicate detection and answers "did this already go out?" a month later.
Assistants go one step further: an MCP upload run skips a task whose exact file or text already went to that stack × brand × platform and reports it as skipped, unless duplicates were allowed explicitly. The hub, the command line and watch-folder jobs keep warning only — you decide.