So I was trying to test “reliability” scenarios, like suggested in documentation, to attempt a reconnection whenever the stream “timeout” (for instance if user internet on mobile device disconnected). At first, it worked fine, but then It stopped working.
To diagnose the issue I tried testing with POSTMAN, and I realize, whenever I connect, then disconnect (by pressing cancel), then try connecting again, I would get this exception returned:
{“title”:“ConnectionException”,“detail”:“This stream is currently at the maximum allowed connection limit.”,“connection_issue”:“TooManyConnections”,“type”:“Twitter API Response Codes & Error Support | Twitter Developer Platform”}
Is this expected ? I am trying some backoff strategies currently since I see it would connect eventually, but I am not sure what is best when working with stream endpoint
2 Likes
Could it be that you hit the 50 connections per 15 minutes limit? Rate limits | Docs | Twitter Developer Platform
