Ctrl K
Reference
Troubleshooting failed posts
What common platform errors mean and how to fix them.
Reading a failure
Open the post and look at the account row that failed. It shows the full reason from the platform. Fix the cause, then use Retry failed accounts; accounts that already published are not posted twice.
Common errors
| Error | Meaning | What to do |
|---|---|---|
| X: HTTP 402 | The X developer project has no API credits. | Add credits in the X developer console, then retry. |
| Pinterest: HTTP 403, Trial access | The Pinterest app only has Trial access and cannot create Pins in production. | Request Standard access for the app, then retry. |
| Instagram: Timeout (2207003) | Instagram could not download the media in time. | Retry. Make sure media links are served from the API’s own public address (PUBLIC_API_URL). |
| Token expired / reconnect | The platform revoked or expired the login. | Reconnect the account under Accounts, then retry. |
| Media rejected | Wrong format, size or count for that platform. | See Platform requirements; swap the file. |
| Rate limited | The platform is throttling requests. | Wait and retry; spread posts out with slots. |
For administrators
- Publishing is done by a worker that runs inside the API process by default (
WORKER_EMBEDDED). A separate worker container is not needed. - The API never runs database migrations; apply schema changes manually.
- Set
PUBLIC_API_URLto the API’s public origin so platforms fetch media directly from it.