Hello! I've noticed I am getting some errors for a tool I made to notify users based on a Typesense query in a Firebase function, and I wanted to see if there is any more info on the Typesense side that can help. I'm not completely sure that it's from my Typesense integration, but I think it is as my logs were similar to the ones from this post: https://threads.typesense.org/2K3424. I am getting the same error logs. Here is my integration in my node.js code: const typesenseClient = new TypesenseClient({ nodes: [ { host: "raccter.com", port: "443", protocol: "https", }, ], apiKey: process.env.TYPESENSE_API_KEY, connectionTimeoutSeconds: 180, }); Then, I am repeatedly querying for search terms with this code: const searchResult = await typesenseClient .collections("listings") .documents() .search({ q: term, query_by: "selectedItem.item,selectedItem.keywords,category,listingDescription", query_by_weights: "0.95,0.3,0.1,0.1", sort_by: "_text_match:desc", prefix: "false", split_join_tokens: "true", min_len_1typo: "4", min_len_2typos: "8", exact_on_single_word_query: "true", match_exclude_terms: "false", }); // Look specifically for the newly created listing ID const matchedHit = searchResult.hits.find( (hit) => hit.document.id === newListingId ); Is there any way I can see if there is more info typesense has? I'm guessing it's something with how my self-hosted vm is responding after several requests in a row? I'm happy to share more info.

It sounds like the server that you're hosting typesense on doesn't have enough capacity to handle the volume of search traffic you're generating, so connections are not being established in time before the client-side timeout is reached

Ok thanks!