Twitter (X) API 503 Service Unavailable Error in n8n Workflow

<Hi n8n Support Team,
I am currently facing an issue while using the Twitter (X) node in my workflow.
Error Details:
“Service unavailable - try again later or consider setting this node to retry automatically (in the node settings)”
HTTP Code: 503
Context:
Node: Create Tweet (Twitter V2)
Operation: Create Tweet
n8n Version: 2.14.2 (Cloud)
Workflow is correctly configured and credentials are connected
What I have tried:
Re-running the workflow multiple times
Verifying credentials
Ensuring valid tweet content
However, the error still occurs intermittently.
Could you please confirm if this is related to Twitter API availability or if there is something missing in my configuration?
Any guidance would be appreciated.!-- Hey! The fastest way to find solutions is by using the :magnifying_glass_tilted_right: search function at the upper right.
If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

Service unavailable - try again later or consider setting this node to retry automatically (in the node settings)

503 - {
  "title": "Service Unavailable",
  "detail": "Service Unavailable",
  "status": 503
}

Share the output returned by the last node

Service unavailable - try again later or consider setting this node to retry automatically (in the node settings)
503 - {
“title”: “Service Unavailable”,
“detail”: “Service Unavailable”,
“status”: 503
}

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Thats Twitter’s API being flaky on their end, not an n8n config issue. 503 means their servers are temporarily refusing requests and its been pretty common with the X API, i would go into the Twitter node settings and enable “Retry on Fail” with a wait time between retries, that way when it hits a 503 itll just automatically try again after a few seconds instead of failing the whole workflow.

did you getit fixed?

the retry approach achamm mentioned is the right call for transient 503s. one other thing to check though: on X API Free or Basic tier the write limits are pretty tight (like 500 tweets/month), so a 503 can also mean rate limit exhaustion rather than just a server hiccup. if it keeps failing after retries, checking your quota in the X Developer Portal usually shows if thats the issue