Skip to main content

Posts & post detail

The Posts page is the record of everything a team has created: drafts, scheduled, published, and failed posts, in a list or on the calendar. Each row opens a detail view with previews, per-channel destinations, engagement, and the actions you can take on a post at its current stage.

The list​

  • Status filter — all, draft, scheduled, published, failed. (An internal publishing state exists while a post is mid-flight — it's transient.)
  • Day filter — arriving from the dashboard's "scheduled today" chip, this scopes the list to one local day and forces the status to scheduled; clear it with the ✕.
  • New Post — opens the composer.
  • Rows show a thumbnail (or the post type), the caption (or a channel title like a YouTube title), status, post type, channel chips, and the scheduled or published time.
  • Hover actions: Edit, Publish now (drafts and scheduled posts, with confirmation), and Delete (with confirmation — this removes the post and its schedule).

The list pages 50 at a time as you scroll.

Post detail​

Detail gives you the full picture of one post:

  • Preview — the platform-rendered preview per linked account (threads render per part).
  • Caption and follow-up comment (if set), and the attached media strip.
  • Engagement — per-channel likes, comments, shares, saves, reach, and impressions once insights have synced.
  • Details rail — status, format, scheduled and published times, created time, and the delay between accounts when one is set.
  • Channels rail — every destination with its platform, name, and per-channel actions where the platform allows: Like/Unlike, Delete from platform (removes the published post on that platform, with confirmation), and View on {platform}.

Actions by state​

StateAvailable actions
DraftEdit, Publish now, Delete
ScheduledEdit, Publish now (skip the wait), Reschedule, Delete
Publishing— (transient; TikTok posts can stay here until the platform confirms)
PublishedEdit, Delete (locally), per-channel Like / Delete on platform / View
FailedEdit, Retry now, Reschedule, Delete

Retry now resets the failed channel schedules and re-enqueues them with a fresh retry budget — use it after fixing the root cause (expired token, rejected media, rate limit).

tip

Publishing is asynchronous. "Publishing…" is always an intermediate state; the real outcome arrives as a notification when the background job resolves.

Publishing outcomes​

A cross-post is one unit, but each channel settles independently: if one channel fails (token expired, platform rejected the media), only that channel is marked failed — the others still ship. The failed row carries the platform's error message so you can edit and retry just that destination.