Troubleshooting Publishing, Queue, and Connections

Overview

Most problems in StretchSocial fall into four buckets: something won't load, you don't have access, a channel is broken, or a post won't move through its lifecycle. This guide walks each one with the exact steps to fix it. Start here when a specific action fails; for quick answers, see the StretchSocial FAQ & Troubleshooting.

A tab or view won't load

1. Click the Refresh button in the top-right, or Retry on the error message — most load errors are transient.
2. If you see "Your session needs to be refreshed," your sign-in expired; refresh the page to re-establish the session, then reopen the tab.
3. If you see "StretchSocial is busy right now," the service is briefly rate-limited; wait a few seconds and retry, then try again in a minute if it persists.

"You do not have access to this view yet"

This means your account lacks permission for a write action — creating posts or connections, approving/rejecting, or scheduling. Reading (dashboards, queue, analytics) is broadly available, but writes require StretchSocial write access. Ask your workspace administrator to grant it, then retry the action.

A post won't save

1. Confirm the Body isn't empty — a caption is required, and the Create/Save button stays disabled without one.
2. Make sure the required fields are complete; the composer won't submit an incomplete post.
3. If you intend to schedule, select at least one target network first.

A post won't schedule or won't reach the queue

1. Confirm the post is approved in the Approvals tab — governed publishing requires approval.
2. Confirm it targets at least one network — each target becomes a queue job, so a post with no networks produces no jobs.
3. Set a valid date/time in Compose → Schedule or via Calendar → Schedule.
4. Remember the seven-day chart only shows the next week; a post dated further out is still scheduled but won't show a bar — check Scheduled posts for the full list.

A queue job shows Failed

1. Open the Queue and read the Error column for the failed row.
2. The most common cause is a disconnected channel. Open Connections and look for a red status chip on the job's network.
3. Re-add or refresh that connection, and confirm with your administrator that live authentication for the network is enabled.
4. Return to Calendar and reschedule the affected post. Because networks are independent, only the failed job needs attention — the others may already have delivered.

A connection shows Disconnected or Pending

1. Open Connections and check the channel's status chip and Last sync time.
2. A Disconnected/Failed (red) channel can't receive posts; re-add or refresh it.
3. A Pending (amber) channel is registered but not yet ready — confirm the account type is right (some networks require a business/creator account) and that your administrator has enabled live authentication.
4. Verify you used the correct platform key (e.g. linkedin, x); twitter is normalized to x automatically.

A network isn't available to target

Only the eleven registry networks are supported, and only seven (LinkedIn, Facebook, Instagram, X, Threads, TikTok, YouTube) can be picked in the composer. If a network is missing, confirm the key against Supported networks and capabilities. Networks marked planned can be planned and scheduled for now, with live delivery enabled by your administrator later.

When to escalate to your administrator

Some things are outside a workspace user's control and need an administrator:

• Enabling live publishing for a network (OAuth, token storage, app review).
• Granting StretchSocial write access to your account.
• Turning on AI drafting or the content-assessment engine.

Tips

• Fix the connection first, then reschedule — most failed jobs trace back to a red channel.
• One failed job doesn't fail the whole post; treat networks independently.
• Keep connection labels brand-prefixed so you fix the right channel the first time.
• If everything looks right but nothing delivers, ask your administrator which networks currently have live publishing enabled — in governed mode, planning succeeds even when delivery is still gated.