Hi,
I got the same problem you faced and I consequently searched for the issue which is in fact a limitation of the Twitter Stream API.
"Each account may create only one standing connection to the public endpoints, and connecting to a public stream more than once with the same account credentials will cause the oldest connection to be disconnected. Clients which make excessive connection attempts (both successful and unsuccessful) run the risk of having their IP automatically banned."
https://dev.twitter.com/docs/streaming-apis/streams/public
Consequently, I cannot do anything to prevent this error from happening.
In the meantime, UserStream are not limited to a specific number of connections but should still be limited in their usage.
Kind Regards,
Linvi
I got the same problem you faced and I consequently searched for the issue which is in fact a limitation of the Twitter Stream API.
"Each account may create only one standing connection to the public endpoints, and connecting to a public stream more than once with the same account credentials will cause the oldest connection to be disconnected. Clients which make excessive connection attempts (both successful and unsuccessful) run the risk of having their IP automatically banned."
https://dev.twitter.com/docs/streaming-apis/streams/public
Consequently, I cannot do anything to prevent this error from happening.
In the meantime, UserStream are not limited to a specific number of connections but should still be limited in their usage.
Kind Regards,
Linvi