Keep posting with an evergreen queue

Some posts are worth making once and sending many times: what time your services are, where to park, how to give, what a first visit is like. An evergreen queue holds those in a pool and works through them on a cadence, so your Page keeps a pulse between the events you actually promote.

Build the queue

Open it from the Campaigns tab

In the Social Hub, open Campaigns and choose Create a queue (or Manage queue if one already exists). Give it a name you will recognise later, like “Welcome & info”.

Add at least two posts

Add a post opens the normal composer, minus the date and time — a pool entry has no clock of its own. Choose Facebook, Instagram, or both. Choosing both makes one shared entry: edit its wording, tags or dates once and both networks get the change.

Warning

Evergreen supports photos only, no video, and any entry targeting Instagram must carry at least one photo.

Set the cadence and activate

Choose how often the queue posts and at what time of day, then activate it. The status chip reads Running. Each network works through its own share of the pool independently, so the cadence means “how often this network posts”, not a combined rate.

The posts in rotation, numbered, with tags, a Next up marker, and per-platform counts — The pool in order. Shared entries appear under both networks; moving one moves both.

Tell Hubl when a post is allowed to run

Rotation details inside a pool entry is where you say more than “post this sometimes”.

Tags — comma-separated labels such as welcome, giving, vbs, saved in lowercase. They do nothing on their own; the sequencing rules below read them.
Start and end dates — limit an entry to a period, both dates included.
Recurring months — for content that comes back every year. February through May for VBS, say. Leave the dates blank and pick All year for a post that is always eligible.

Date and month limits both apply when both are set, and both are read in your organization’s timezone.

Keep it from sounding like a loop

Settings on the queue holds the rules that stop the rotation reading like a rotation:

Sequencing — avoid consecutive posts carrying the same tag, or set a minimum number of days between them. Rules are measured against each network’s own published history.
Spacing — skip to the next occurrence when another post is already going out too close to this one on the same network. Include event and campaign posts, and those get priority.
Blackout dates — ranges the queue sits out without advancing its rotation.

Note

If every eligible post would break a sequencing rule, the queue relaxes that rule rather than going silent, and marks the post Sequencing relaxed. It never relaxes date or month limits: a seasonal pool with nothing currently eligible stays active and simply waits.

Tip

Existing queues have no spacing, sequencing or blackout rules until you add them. If your queue has been running a while and feels repetitive, this is the first place to look.

Check what it is about to do

Upcoming posts at the top of the queue shows the next runs per network.

Upcoming evergreen posts listed per platform with Scheduled and Projected labels — Scheduled entries are already committed. Projected ones are Hubl's best guess at what comes next.

Scheduled — already saved, and it will publish as shown. Editing the pool entry does not rewrite a snapshot that has already been taken.
Projected — what the queue would pick next, assuming everything publishes and neither the pool nor the schedule changes. Treat it as a forecast.

Tip

One network showing the same post over and over in the projection usually means only one entry is currently eligible for it. Check the month and date limits on the rest — a VBS post restricted to February through May is invisible in September.

Pausing, stopping and failures

Pause holds the rotation; Cancel stops the queue and cancels anything it had already scheduled. The pool itself survives both, so restarting does not mean rewriting your posts.

Organization administrators get an in-app alert when an evergreen post fails, and when an empty queue pauses itself. Turn on email alerts in queue settings to get those by mail too. Retry a failed post from the Social Hub timeline, the same as any other — see When a post fails or the account disconnects.