Content recycling
Repeat evergreen posts safely with finite plans and rotating copy.
- Documentation owner:
- BlendDuck Documentation
- Last reviewed:
Content recycling creates future copies of an existing multi-channel post on a weekly or monthly cadence. Every copy still passes the normal channel, media, platform, scheduling, idempotency, publishing, and audit pipeline.
Make a post recurring
Open a post in Calendar, open its more menu, and choose Make recurring. Choose a weekly or monthly gap and set a repeat count, an expiry date, or both. BlendDuck requires a finite boundary; when both are set, the first boundary stops the plan.
The optional first-repeat field uses your IANA timezone. Leave it blank to keep the source cadence. Weekly and monthly repeats preserve local wall time across daylight-saving changes, and month-end dates remain anchored (January 31 → February 28 → March 31).
Rotate content variations
Add up to 20 alternatives. They rotate in order by durable occurrence number:
two variants produce A, B, A, B. A retry keeps the same variant and request
identity, so it cannot advance the rotation or create another copy.
X and Pinterest show a warning when a plan repeats identical copy. YouTube and TikTok are excluded from automatic recycling and fail before a plan is saved. Each channel can belong to at most 10 open recycling plans.
Follow, retry, or stop
Use Recycling in the Calendar header to inspect active and historical plans. Each occurrence shows its schedule, variant, attempt count, created post identity, and failure evidence. A failed occurrence can be retried. Stop prevents future materialization but leaves copies already scheduled in the calendar under the normal post lifecycle.
If BlendDuck was unavailable until a repeat was already stale, that occurrence is recorded as skipped and the original cadence advances. It does not publish a burst of overdue content.
If an occurrence keeps failing, record the request ID and provider error before contacting support. Do not recreate the entire plan: retry the failed occurrence or stop the plan and create a corrected one.