A Slash Social action did not complete

An action can fail in a Slack modal, App Home, a message action, or a slash-command flow. Start with the visible error and the active brand before retrying.

Symptoms

You may see an inline validation message, a Slack confirmation that does not change the expected item, an action that stays disabled, or a modal that closes without showing the expected updated state. Record the exact message before you close the modal. The wording, action name, active brand, and time of the attempt help distinguish an access problem from a stale item or connected-account problem.

Checks

Check the active brand and your access

1. Open App Home and confirm the active brand.
2. Reopen the action from its normal entry point.
3. If the action is missing or blocked, ask a brand administrator to confirm your role and any plan requirement.

An action that uses the wrong brand, a missing account, or insufficient access does not make a partial change.

Check the action input

1. Read the inline validation message or Slack feedback.
2. Correct required fields, selections, dates, or platform choices.
3. Submit once more from the refreshed modal.

Do not reuse a stale modal after another teammate changes the same item. Close it, reopen the item, and apply the change again.

Fixes

Check the connected account or service

If the action publishes, imports, syncs, or sends a notification, confirm the connected account is healthy and the target Slack channel is available. See Account connection expired for OAuth recovery and Notifications are missing for delivery checks.

If the action changes a schedule, approval, campaign, or configuration, open the current record again before retrying. Another teammate may have changed it after you opened the prior modal. Apply the action from the refreshed record so Slack validates the latest state.

Recovery

If retrying from a fresh modal still fails, stop repeated submissions. Repeated retries can create duplicate drafts, duplicate notifications, or conflicting scheduling requests when the original action actually completed after Slack timed out. Check the affected list or item first. If the intended change is already visible, no recovery action is required.

For a failed generation, open the Failed Jobs view and use the documented retry path. For publishing failures, use Publishing failed so you can check account health and platform-specific validation before you resubmit.

When an action opens a browser authorization page, return to the original Slack modal after you finish. Confirm the account list or item state refreshes before you retry another action. Starting a second authorization flow before the first flow finishes can leave you with an unclear result and makes the visible error harder to interpret.

Record any reference number Slack shows with the failure.

Prevent it next time

Confirm the active brand before a multi-step action, complete required fields in one open modal, and reopen the record after another teammate makes a change. For actions that publish or schedule content, verify the account connection and target platform before the final submit. Use the visible error text as the starting point rather than guessing at a browser or cache workaround.

Contact support

Send the action name, the active brand, the time of the attempt with timezone, the exact visible error text, and the steps you already tried. Do not send passwords, OAuth tokens, private keys, or unnecessary personal data.