Freshness guardrails

Better a visible skip than a stale post.

After downtime, lesser tools dump a backlog at 3 AM. QueueTempo marks old occurrences as skipped, processes at most the freshest missed slot within a grace window, and keeps the next regular occurrence exactly where it was.

  • Grace-window logic
  • No backlog bursts
  • Skips are visible

The rules of a clean skip

An occurrence more than fifteen minutes past its window becomes skipped_missed_window unless a provider publish was already in flight. Skipped slots explain themselves in history, spend no credits, and never shift the underlying cadence.

  • No publishing after a revoked connection
  • No publishing content that failed validation
  • No firing a burst after downtime catches up
  • No silently swapping destinations to rescue a slot

Why audiences notice

Feeds reward presence, not volume spikes. A steady rhythm with occasional honest gaps reads as reliability; a 2 AM apology-purge reads as malfunction.

Straight answers

Questions, answered.

Is the grace window configurable?

The default is fifteen minutes and the window is configuration-driven, covered by tests so behavior stays predictable.

Do skipped occurrences consume AI credits or allowance?

No. Credits settle only for usable drafts and allowance only for successful platform-accepted targets.

Can I recover a skipped slot manually?

Copy the draft to a fresh one-off slot or wait for the next natural occurrence; the original skip stays in history as a record.

Set the next beat

Ready to set your first Tempo?

Start free, describe your brand once, and watch the next ten post times appear before anything goes live.