የSmartERP መመሪያ የAshewa Technology Solutions መድረክ
ይህ ገጽ ገና ወደ አማርኛ አልተተረጎመም። የእንግሊዝኛው ጽሑፍ ቀርቧል።

Content calendar, backlog and the retry queue

Three screens for planning what goes out when, and recovering from a failed publish.

Three menus under Social Media → AI Workforce cover planning and recovery, separate from the approval and governance screens.

Content Calendar#

Social Media → AI Workforce → Content Calendar shows every post with a Scheduled Date on a month view, coloured by campaign. Switch to list view (the Content Plan list) for a denser view with columns for campaign, agent, character count, link count, views and engagement.

Filters: Not Scheduled, Needs Approval, Upcoming (the default), Published, AI Generated. Group by Campaign, Agent, Status, or Scheduled Month.

A post without a Scheduled Date never appears on the calendar — give it one, or find it in the Unscheduled Backlog below.

Unscheduled Backlog#

Social Media → AI Workforce → Unscheduled Backlog is the same post list, pre-filtered to posts with no scheduled date that are not yet posted or cancelled. This is where drafts and AI-generated content wait until someone decides when they should go out.

Work through the backlog by opening a post, setting Scheduled Date, and pressing Schedule (after approval, if required — see Approval queue and states).

Retry Queue#

Social Media → AI Workforce → Retry Queue lists every post currently in backoff after a failed scheduled-publish attempt: next_retry_at is set and the cron has not yet tried again.

ColumnMeaning
AttemptsHow many times the cron has tried this post so far.
Next RetryWhen the cron will try again automatically.
Failure ReasonThe error from the most recent attempt.

Press Retry Now (on the list row, or the button on the post form) to skip the wait and have the next cron tick try again immediately — useful once you have actually fixed the problem (reconnected an account, renewed a token) and do not want to wait out a 45-minute backoff.

A post leaves this queue the moment it publishes successfully, or once it exhausts its retry budget and becomes Failed. See Scheduled publishing for the backoff schedule and retry limit.

Note

The queue's domain is next_retry_at != False. A post that has already failed permanently (state Failed, no further retries scheduled) does not appear here — find it with the Content Plan list's search, or from the activity log filtered to Publishing.

መጨረሻ የተሻሻለው: 2026-11-15