Skip to content
Sign inStart 7-day trialStart trial
Reliability

A scheduled post should never fail quietly

NioConnect treats a silently failed post as the one unacceptable outcome, and builds everything around making it impossible.

Start 7-day trialSee pricing
Try it

Run a publish, then recover a failure.

Three posts go out. One fails with a plain reason, and Retry sends only that channel.

Scheduled for todayA post reads Posted only after the platform confirms it.

Run the schedule
  • Release notes are liveBlueskyScheduled
    1. Scheduled
    2. Queued
    3. Publishing
    4. Posted

    Waiting for its time.

  • Behind the buildMastodonScheduled
    1. Scheduled
    2. Queued
    3. Publishing
    4. Posted

    Waiting for its time.

  • Weekly roundupTelegramScheduled
    1. Scheduled
    2. Queued
    3. Publishing
    4. Posted

    Waiting for its time.

The life of a post

A closed set of states. A post is always in exactly one of them.

  1. Draft

    Draft

    Written, not yet scheduled.

  2. Scheduled

    Scheduled

    Validated and waiting for its time, or for approval.

  3. Publishing

    Queued and publishing

    Handed to the publisher and being sent.

  4. Published

    Published or failed

    Confirmed by the platform, or failed with a reason.

Under the hood

It heals itself. It never posts twice.

A reconciler heals what slips

If a queued post is lost, or a publishing post gets stuck, the reconciler finds it and puts it back on track. Nothing relies on a single process staying alive.

  • Queued posts are checked and restored
  • Stuck publishing posts are recovered
  • The database is the source of truth
See the calendar

Published once, even after a retry

Each post carries a key that is created before the platform is called. Before any retry, NioConnect reads back what the platform already has, so a post does not appear twice.

  • Key created before the call
  • Read back before repost
  • Retries only when it is safe
Compose per platform
Honesty

Four promises about status

Never optimistic

Published means the platform said so.

Plain reasons

Failures come from a closed list, written for people.

Safe retries

Only errors that can succeed later are retried.

Live updates

Status changes appear without a refresh.

Frequently asked questions

Can't find your answer?

Can you promise a post will always publish?
No platform guarantees that. What we promise is that a post never fails silently: it is retried when that is safe, and otherwise it tells you why.
What happens when a channel needs reconnecting?
Affected posts fail with a clear reason and the channel shows as needing attention until you reconnect it.
Does an emergency stop exist?
Yes. An organization can pause publishing in one action.

Reliability is part of every plan

There is no premium tier for posts that arrive. Every plan gets the same reconciler and the same rules.

Start 7-day trialCompare plans

Ready for posts that go out when you said?

Start your 7-day trial, or compare plans first.

Start 7-day trialSee pricing