Skip to main content

Troubleshooting

Start with the error shown on the affected post or account. A successful save or schedule operation does not guarantee that every social platform accepted the post.

Connection errors​

Open Accounts and choose Reconnect for an expired or revoked connection. Sign in as the intended identity and grant the requested permissions. Confirm that you still manage the Page/channel and that the account meets the platform requirements.

If no accounts appear after OAuth, check page/channel permissions. If pending account selection has expired, restart from Accounts. Hosted users should not create their own developer app to troubleshoot an ordinary hosted connection.

Failed or partially published posts​

  1. Open Posts → Failed, then the affected post.
  2. Check the result and published link for every target account. A failed overall status can include successful publications.
  3. Fix the cause: reconnect the account, adjust content/media, restore subscription access, or choose permitted platform settings.
  4. Choose Edit and Retry. The retry form selects accounts without recorded success; review that selection and do not reselect successful targets unless you intend another post.
  5. Publish now or choose a new future time. A retry creates a new post record and can consume allowance.

If the outcome is uncertain after a timeout, inspect the post and the social platform before retrying. API callers should reuse the same idempotency key and payload after an uncertain response. Never send a fresh create request simply because the first response was lost. API retry guidance.

Billing and allowance errors​

Read plans and allowances. Trial usage is per target account on each platform; paid usage is per saved post record. Posts due after expiry become failed and need review and retry after subscribing. Upgrading does not automatically send them.

Media and validation errors​

Use a supported file type and size and complete all required fields. Instagram needs media, YouTube needs a video, and Pinterest needs a board. Some platforms do not accept mixed image/video posts. Publishing guide · Platform matrix.

For remote APIs and MCP, media URLs must be publicly fetchable. A local path, private cloud link, or blob: URL is not sufficient. If your assistant cannot expose an attached image as a file parameter, upload it in the web app or provide a public URL.

Assistant connection errors​

Use the direct ChatGPT or Claude setup instructions for hosted SimplePost. Other clients must support remote MCP and OAuth. Sign in to the same SimplePost account that holds your social connections. If access was revoked or expired, reconnect in the assistant. Your assistant plan or workspace administrator can restrict available integrations.

The app's CLI tab assumes the CLI is installed. Run npm install -g @simple-post/cli, then follow CLI setup. Hosted CLI access requires Advanced, Pro, or an active trial.

Scheduling errors​

Choose a future time and check the displayed timezone. Posting slots are suggestions, not automatic recurring posts. Credential changes, media changes, or access expiry between creation and dispatch can cause a scheduled post to fail. Scheduling guide.

Need help?​

Contact SimplePost. Include the post ID, platform, time, and the error message. Do not send passwords, access tokens, API keys, or bot tokens. Documentation and support remain available after trial expiry.