How-to guide

Resume, reassign, or repair Quick Start

Follow the complete Slack workflow to resume, reassign, or repair quick start, including prerequisites, decisions, and recovery steps.

Goal

Resume the exact Quick Start object, reassign setup, or repair a blocker without resetting canonical data.

When to use this

Use this workflow when:

You closed brand direction, Composer, account connection, checkout, or an approval handoff.
Generation, account connection, or access failed.
Someone else should complete first-brand setup.
A delegated operator needs to return the assignment.

Before you begin

Confirm the active brand and your permission to view it. Recovery must preserve the canonical Post, approval, schedule, and pending-intent records.

Steps

Resume Quick Start

Open Slash Social App Home.
Follow the Quick Start primary action for the authoritative state.
If the first Post was already saved, open it from Create and retry the intended action there.
Complete any missing prerequisite. Account connection, approval routing, or checkout appears only when the selected Post action requires it.

Delegate or return setup

Select Delegate setup to choose an eligible teammate.
Confirm the teammate received setup-manager access without billing or ownership authority.
A delegated operator who cannot continue selects Decline setup.
An eligible administrator can then continue or choose another teammate.

Repair a failed handoff

Open the canonical Post, approval, assignment, or schedule referenced by the recovery action.
Confirm the active brand and required permission.
Retry once from the offered canonical action.
If authorization or prerequisites changed, follow the rerouted action.

Slash Social does not restore the retired checklist/tour. Recovery projects forward from durable records and must be idempotent.

Recover by destination

Use the destination that owns the durable result:

Open Create for a saved Post, an unfinished compose session, or failed generation.
Open Approvals for teammate or client review work.
Open Calendar for a saved schedule or a scheduling conflict.
Open Settings for brand direction, account connection, pillars, cadence, approval routing, or billing prerequisites.

Do not create a replacement Post merely because a later action failed. A generation error, disconnected account, unavailable reviewer, or payment prerequisite can block the next motion without invalidating the Post that already exists.

Handle common interruption points

Brand direction was not accepted

Return to App Home and select Review brand direction. Edit the suggested direction, confirm its source, and accept it before reopening Composer.

Composer was closed before save

Select Resume Composer. Confirm the active brand before editing. If the durable compose session is no longer available, start a new Post with the accepted brand direction; do not duplicate a Post that is already visible in Create.

Generation failed

Open failed work from Quick Start or Create. Retry the existing job once. Quick Start remains incomplete until a canonical Post is saved, so a failed generation attempt does not falsely mark setup complete.

An account connection is required

The selected motion needs a publishing target. Reconnect or choose an eligible account from Settings, then return to the same Post. Keeping the Post as a draft remains available without a connection.

A review handoff is no longer valid

Open the Post in Create or the review in Approvals. Select an eligible reviewer or choose another allowed motion. Do not attempt to revive an assignment for someone who no longer has access.

Escalate without exposing content

If the offered recovery action cannot proceed, record the Slack workspace, active brand, affected destination, approximate time, and visible error reference. Include the Post or approval link when it is safe to share. Do not send access tokens, social credentials, private Post copy, or customer data in a support request.

Confirm it worked

The same valid object and action reopen.
Existing Posts, approvals, and schedules remain in their canonical destinations.
Retrying does not create duplicate objects or side effects.
The setup assignment is visible only to authorized actors.

Close and reopen Slack once more after recovery. The same canonical object should remain available, and App Home should show the current action rather than an earlier first-run state.

Troubleshooting

App Home looks unchanged

Switch to another Slack tab, return to Slash Social, and reopen the canonical destination. App Home refreshes from authoritative records.

Generation fails

See Recover failed jobs for retry paths from Create and App Home.

The assignment is no longer valid

Refresh App Home. Continue only when Slash Social shows an authorized Quick Start assignment or ask an administrator to delegate setup again.

A safe replacement action appears

The original pending action no longer has a valid object, permission, or prerequisite. Follow the replacement action. This is expected forward recovery and does not mean that saved brand or Post data was lost.

You see duplicate work after retrying

Stop retrying and inspect Create, Approvals, and Calendar for the existing object. Capture links to any duplicates and contact support. Do not delete records until the team confirms which object owns the valid history.