Why can't I post to X (Twitter)?
Updated 6 months ago
If your X (Twitter) account is already connected in Metricool but your post fails to publish, the issue is usually related to account authorization, accepted permissions, or a temporary X outage. Use this guide to identify the error type and apply the fastest fix.
Before you start, try publishing directly on X with the same account. If you cannot post there either, the issue is not coming from Metricool.
Identify the error type
These are the most common errors when publishing to X after the account is already connected:
Invalid or expired token or 401 Unauthorized: the X authorization has expired or is no longer valid.
Error sending request: the request did not reach X correctly. Reconnecting the account usually fixes it.
500 or 503 Service Unavailable: this is a temporary X issue. In most cases, you only need to wait and try again.
Reconnect and reauthorize your X account
When you reconnect your account, use an incognito window if possible. This helps prevent conflicts with old sessions or stored cookies during the authorization flow.
Open Metricool and go to the connections dashboard.
Disconnect the X account that is showing the error.
Connect the account again in an incognito window.
Log in to X when the authorization window opens.
Accept all requested permissions. If X shows two authorization steps, accept both.
Try publishing again.
Check account permissions
Your account must still have valid permissions on X to publish. If you changed your password, revoked app access, or had a security check on the account, the connection may stop working even if it still appears connected in Metricool.
In that case, disconnect the account and complete the connection again to generate a new OAuth authorization.
If you see a 500 or 503 error, do not disconnect the account right away. This is a temporary X outage. Wait a few minutes and try to publish again or reschedule the post.
When to reconnect and when to wait
Reconnect the account if you see a token, authorization, or permissions error.
Wait and try again if you see a 500 or 503 error.
Check the account directly on X if you cannot publish there either.
If you need help with the initial connection or with an error during the first connection flow, see I can't connect X (Twitter). If you want to review the normal publishing flow and content requirements, see Schedule and publish on X (Twitter).