As the full page screenshot of my entire workflow called social media post automation shows that I have integrated both Facebook page and X account using HTTP nodes.
Problem : - described based on the case observed
- The schedule trigger was set with 10 minutes interval at 23:31 and let it continue till 02:11. within this time frame, Facebook posts were published smoothly without any after each 10 minutes interval.
- But the problem was with X account. Though the first two X posts were published as expected, the third one was skipped. Then it kept posting each 10 minutes interval except a double posting at 1:01 as the previous post was at 1:10. However, although I continued the workflow till 02:11, X account stopped posting at 01:11.
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:
Hi @Md_Farid_Hossain,
Could you please share the execution error logs that show any errors on the third attempt to post?
Hi @Md_Farid_Hossain,
Thank you for the detailed screenshots,
From what I can see, it looks like you’re hitting a rate limit. If you’re using the free tier of X’s API, you’re allowed only 17 requests within a 24-hour period. Once you exceed that, you’ll start seeing errors or skipped posts.
Since you mentioned that you’re triggering posts every 10 minutes, that would reach the 17-request limit in less than 3 hours. That would explain why some posts were skipped or stopped altogether after a certain point.
Thanks for you such rapid feedback. But I have got another point to share with you.
Earlier I set longer interval like 4 or 6 hours still, in that case there was no trigger at all meaning no post was published, in this case though the post content size was longer like 3-4 hundred words, while the post content size of the workflow tested with 10 minutes interval was nearly three times shorter.
No problems, @Md_Farid_Hossain
That sounds like a separate issue. I’d do the same, open the execution logs and check what the response says If it mentions something like a restriction on tweet size, that could be a clue…
It’s hard to say exactly what the issue is without seeing the specific error message…
