Scheduled publishing

The base module has a scheduled_date field that nothing acts on. This module makes it real with a scheduled action that publishes posts when their time comes.

The action#

Settings → Technical → Scheduled Actions → "Social: Publish Scheduled Posts"

Posts beyond 50 wait for the next run. A post is published at the first run after its scheduled time, so allow up to five minutes of slack.

One failure does not stop the rest#

Each post is processed and committed on its own. If one fails:

1. its transaction is rolled back;
2. the post is set to Failed with the error in Failure Reason;
3. a Publish Failed entry is written to the activity log, with trigger "Scheduled publishing cron";
4. the loop continues with the next post.

So a broken Telegram token cannot stop your Facebook posts from going out, and the failure is on the record rather than lost in a server log. The server log gets a warning line too.

After a run, an info line reports how many were published and how many failed.

Fixing a failed post#

Open the post: Failure Reason says why. Fix the cause (a token, a channel, a bad character), then either:

• press Submit for Approval again to go through the queue, or
• have a Manager press Publish.

A Reset to Draft clears the failure reason and lets you start over.

The two other actions#

The module also creates two hourly actions. They ship inactive, because they call the live platform APIs:

Turn them on once real accounts are connected. See Scheduled actions.

Using n8n instead#

If you publish through n8n, deactivate Social: Publish Scheduled Posts, so the two do not race for the same post. See Auto-publish workflow.