4 months ago
I created the adp_twitter_bot that sends a tweet once an hour, I'm using the Railway cron feature for this. But I'm seeing this in the logs starting last night around 1:00 am Eastern time. Unfortunately when I cut and paste from the logs, it doesn't include the time stamps, but you get the drift.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Starting Container
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Starting Container
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 900 seconds.
Starting Container
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Starting Container
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Starting Container
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Rate limit exceeded. Sleeping for 901 seconds.
Starting Container
Rate limit exceeded. Sleeping for 901 seconds.
2 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 5 months ago
4 months ago
Youre hitting twitter's rate limit, you probably misconfigured the cron and its in a constant loop