Retry a failed generation

Generation and publishing jobs can fail after you create or schedule a post. Slash Social surfaces those failures in Slack so you can read the reason, fix the blocker, and retry without starting from scratch.

Symptoms

• A direct message reports that generation failed or publishing failed.
• App Home Recent Failures lists a job you expected to succeed.
• The Create work center shows a failed count that matches jobs you cannot open as drafts.
• A draft stays in generation failed state and does not move to approval or publish.
• Running /social and searching for retry or failed shows a retry task for the same item.

You need a failed job visible in App Home, a DM, Create, or the retry task in /social before you can recover it.

Checks

Before you retry, confirm what failed:

1. Open the failure from the DM, App Home Recent Failures, the Create work center failed count, or /social (search for retry or failed).
2. Read the failure reason shown in the details. Note whether it mentions media, account connection, schedule windows, or limits.
3. Confirm the affected brand and platform match the post you were creating.
4. Fix the reported blocker before you tap Retry (missing media, disconnected account, queue window, or exhausted limit).

Likely causes:

• Required media was missing or not ready when generation ran.
• The target social profile was disconnected or expired.
• The scheduled slot fell outside an allowed posting window.
• A plan or usage limit blocked the job.

Fixes

1. Open the failure surface you already have: the failed-job DM, App Home Recent Failures, the Create work center failed count, or /social with retry or failed in the search.
2. Review the failure reason in the details modal or message. Do not retry until you understand the blocker.
3. Fix the underlying issue (attach media, reconnect the account, pick a valid schedule time, or resolve a limit message).
4. Tap Retry on the failure card or follow the retry action in the details view.
5. Wait for the job to finish. A successful retry moves the item toward draft saved, queued, or pending approval depending on your workflow.
6. Open the item in Create after retry when you need to confirm media or copy before approval.

If the failure count on Create and the list in Recent Failures disagree, use the failed-job list as the source of truth and retry from that surface so scope matches the count.

See Create and schedule a post for the happy-path flow generation should return to.

Confirm the fix

The failure disappears from Recent Failures and the Create failed count drops. The item opens in Create or review without a generation failed label, and you can continue editing, approving, or publishing.

Prevent it next time

• Attach required media and confirm account health before you queue generation.
• Schedule inside brand cadence windows when your post has a slot time.
• Watch Create and App Home failure counts so you catch issues before publish day.
• Read the failure reason on the first attempt instead of retrying repeatedly without changes.
• When a DM failure arrives, fix the blocker before you dismiss the message so you do not lose the retry action.

Contact support

If retry fails again, open the failure details and fix the new blocker before another attempt.

When retry keeps failing, contact support with the job ID (if shown), affected brand, platform, connected account, and the exact error text from the failure details. Include whether the failure was generation or publishing.