Troubleshooting

Operator-level guidance for the conditions most often encountered during a pilot. Each entry points at the evidence that explains the state rather than at a repair procedure.

A campaign is not ready for generation

Campaign grounding is incomplete. Confirm the campaign has an audience, theme, call to action, landing URL, platform selection, and an active phase, and that its status is one of Draft, Active, Paused, Completed, or Archived. See Campaigns.

A story has no usable source snapshot

The story has a source brief but no stored content snapshot, so there is nothing to ground a claim in. Add or restore the source material and re-check the story before generating. See Stories.

Generated content is not appearing in the review editor

Check, in order: whether master generation is enabled, whether generation configuration reports ready, whether a generation limit was reached, and whether the story is grounded. See Content Generation.

A visual is not approved or current

The attached asset is either unapproved or is not the current visual for the post. Approve the intended asset and confirm the association on the story. See Assets.

A scheduled post appears twice on the calendar

Two schedule records exist for the same story and destination, usually because a schedule was re-created without the earlier record being cancelled. Treat Publications as authoritative, cancel the superseded record, and re-check the calendar.

A destination is not eligible for the workspace

The destination is inactive, unmapped, or owned by another workspace. Confirm the account in Accounts and the mapping in Buffer Destinations.

A publication failed before send

A safety gate refused the execution and nothing reached the platform. Read the recorded reason on the publication record, resolve the underlying condition — approval, ownership, eligibility, or asset state — and reschedule. See Publication Safety.

Buffer contains a post that is not verified in RI Social Media

The governed record is the source of truth. Reconcile using the Buffer Execution Log to match the outbound request and returned identifier to the publication record before taking any action at the platform.

Media storage reports a warning or conflict

An object is unverified, mis-owned, or still in legacy read-only storage. Resolve the storage state before publishing anything that depends on that asset. See Media Storage.

Publication remains disabled

Global publication enablement is off, or readiness reports a blocked check. This is the expected pilot posture. Enable publication only after readiness passes and the acceptance criteria in Getting Started are met.

Last updated 1 month ago