That maybe the issue. I have yet to test such a usecase. I've already preemptively added a feature ticket to rewrite how connections activity are pulled from the database to avoid massive IN values (in your case the IN statement in SQL is over 2500 values).And yes, the thought just occurred to me as well that maybe it has something to do with the large amount of connections. I have nearly 2500 connections, mainly because most people accept the automatic connection request.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.