Skip to main content

Recurrence & evergreen content

Recurrence lets a single piece of content repeat on a schedule — daily, weekly, or monthly — optionally capped at a number of repeats. It's the mechanism behind evergreen content: posts that stay valuable and stay in rotation without manual re-scheduling.

How it works​

A recurrence rule attaches to a post at the moment you first schedule it (the Repeat row in the composer's final step — it's create-only; an existing post can't gain a rule later). A rule describes:

  • Interval + unit — every 1–365 days, weeks, or months.
  • Max repeats — optional; leave it empty for unlimited.

When a recurrence fires, post.buzz clones the post — caption, media (in their original order), post type, destinations — as a fresh scheduled instance, then advances the rule. If the rule fell behind (say the scheduler was paused), it catches up with a single clone for the current window rather than spamming one per missed interval.

The rule lifecycle​

  • One rule per post. Re-creating a rule on the same post replaces the cadence and resets the count.
  • Pause / resume — a paused rule keeps its place; resuming continues from the next interval.
  • Auto-deactivation — a rule deactivates itself (cleanly, not as an error) when it hits max repeats, when its source post is deleted, when it has no remaining channels, or when its interval is invalid.
  • Editing the interval or unit recomputes the next run from the current next-run time.

When to use recurrence​

  • Evergreen tips and CTAs — short, durable posts worth repeating.
  • Weekly series — "Feature Friday," "Monday motivation."
  • Timeless promotions — recurring links to a flagship product or lead magnet.

Avoid recurrence for time-sensitive content (announcements, news, limited-time offers) — those should be one-off scheduled posts.

Limits and safety​

Recurrence respects the same guardrails as everything else:

  • Per-account minPostGapMinutes — no bursts.
  • Plan limits — monthly post caps still apply to clones.
  • Platform limits — each cloned post is validated before publishing.

If a recurrence would exceed a limit, the instance is skipped or held, and the reason is surfaced so you can adjust. Media used by a post with an active recurrence can't be deleted from the library — the guard names the blocking posts.