When accessing Twitter via Nimble over the Twitter API, we are subject to certain API limits on their network. Every user has a certain amount of requests they can send (via Nimble) to the servers. This ensures a good user experience for all the users in the Twitter network.
If you receive a message from Nimble, "You have reached the maximum number of requests. Information and updates from this network may be unavailable to you for a short time", it means you have reached the request limit for a particular action over the Twitter API.
The main case for the Twitter API will be if you are viewing your Notifications in the Signals tab and view over 75 notifications within a 15 minute time period.
If you receive this limit notification, you have a few options:
Wait 15 minutes and then resume your work.
Use the Nimble Prospector extension on twitter.com/notifications to continue interacting with your notifications alongside Nimble.
If you have any questions, please write us at care@nimble.com, initiate a chat from this FAQ, or join one of our Nimble Onboarding and Best Practices sessions, held every weekday at 9 AM PT.