Auto-Recycle
Schedule up to 3 reposts and 3 reshares the moment you compose, with delays from 1 hour to 1 year. Same picker in composer, calendar modal, and chat publish dock.
What Auto-Recycle is for
Auto-Recycle keeps evergreen content circulating without you opening the calendar every week. You decide the recycle plan at compose time, attach it to the source post, and Aidelly auto-schedules each repost and reshare at the configured offsets the moment the source publishes.
- Repost — the platform's native re-broadcast (where supported).
- Reshare — a fresh copy of the post published as a new entry.
Useful when the same post deserves multiple impressions across a week, month, or quarter — and you don't want to babysit it.
Where it lives
Three surfaces, identical UI:
- The post composer at
/post— the main entry point. - The calendar schedule modal when editing a scheduled post.
- The chat publish-confirm dock when an agent is about to publish on your behalf.
All three render the same RecycleSchedulePicker component, so behavior is identical everywhere.
Limits
| Setting | Value |
|---|---|
| Reposts per source | Up to 3 |
| Reshares per source | Up to 3 |
| Total recycles per source | Up to 6 |
| Minimum offset | 1 hour |
| Maximum offset | ~1 year |
| Far-out threshold (warning) | 30 days |
The 3-per-kind cap matches the existing MAX_PENDING_RESHARES_PER_SOURCE and is enforced at the schema layer — runaway rules are not possible.
Step 1 — Open the Auto-recycle panel
In any of the three surfaces, below the schedule picker you'll see a collapsible "Auto-recycle this post" section. Click to expand.
It has two chip rows:
- Repost — one chip per scheduled repost. Disabled on platforms where the platform itself doesn't support native repost.
- Reshare — one chip per scheduled reshare. Available on every platform Aidelly publishes to.
Step 2 — Add a recycle
Click the + chip on either row. A new entry appears with a default offset (Reshare: +1w; Repost: +1d). The chip shows the offset label, e.g. +3d, +2w, +1mo.
Step 3 — Pick an offset
Each entry has a custom-offset input. Tap the chip to open the offset editor:
- Pick a unit: h (hours), d (days), w (weeks), mo (months).
- Type a count. The chip label updates live (e.g.
+3w). - If the resulting absolute time is more than 30 days out, the entry shows a "far-out" warning — useful to know but not blocking.
Step 4 — Remove or reorder
- Remove — click the
×next to a chip. - Reorder — recycles are sorted by offset automatically; you don't need to drag.
Step 5 — Ship it
Publish or schedule the source post like normal. The recycle entries persist with the source. The moment the source publishes, Aidelly auto-schedules each recycle at source_published_at + offset.
What appears on the calendar
Each recycle becomes its own scheduled_posts row linked to the source via source_post_id. On the calendar:
- The recycle shows up at its computed time with a small recycle badge (🔁 for reshare, ↻ for repost).
- The badge links back to the source post.
- Cancel or edit a recycle the same way you would any scheduled post.
How Auto-Recycle interacts with other Aidelly features
- Posting Cooldowns — a recycle that would land during a cooldown is nudged to the next valid slot.
- Crosspost Routes — recycles inherit the source's route fanout; a single recycle entry can fan out to every destination.
- Automation Queues — when a recycle hits a per-account queue, it enters the queue tail.
- Calendar — recycle badges + drag-to-reschedule per recycle row.
- Warning Rules — alerts on stale recycles you might want to clean up.
Editing after publish
Recycle entries are first-class scheduled_posts rows, so you can:
- Cancel a single recycle from its row on the calendar.
- Add new recycles from the post detail drawer → "Auto-recycle" section after the source has published.
- Edit a recycle's caption or media independently of the source.
Troubleshooting
- Repost chip greyed out — the platform you picked doesn't support native repost. Use Reshare instead.
- "Far-out" warning won't go away — the offset is > 30 days. It's just an FYI; you can keep it.
- Recycle landed in a quiet window — Aidelly nudges to the next valid slot. Check the post's audit trail for the nudge event.
Related guides
- Posting Cooldowns — throttles that apply to recycles
- Crosspost Routes — how recycles interact with fanout
- Automation Queues — slot-aware recycling
- Content Calendar — where every recycle becomes visible