Hi @Ara_Threlfall,
You were redirected from the SERVER project in Jira because there wasn’t enough information for the team to investigate or suspect a possible server issue. There is no server-side caching of queries and your described scenario involves multiple drivers and applications interacting with data. If a minimal, reproducible test case can be created that clearly implicates server (or driver) behaviour, it would then be appropriate to create an issue in the relevant queue.
Assistance via a public forum requires a collaborative approach. We do not have access to your environment, your code, or your data and are trying to construct theories or reproduction cases based on the information provided. Someone asking for information may not be able to provide a solution, but additional details can be useful for others to provide suggestions and help you work through the problem.
The behaviour you are describing seems to be specific to your implementation (which you are understandably unable to share) and does not appear to be reproducible given the details you have provided so far. If the data is queryable as expected in Compass, my best guess would be an issue with your Node.js application. Since there was an issue with the synthetic example provided, I suggest asking a work colleague to review your application code in case there is something you may have overlooked.
If you need dedicated support or consulting time, there are commercial options which are outside the scope of this community channel.
Community members are volunteering their time to try to help you succeed. We expect all members to adhere to our MongoDB Code of Conduct including being positive, respectful, and considerate. Please take a moment to review these guidelines and assume best intent in your future interactions.
Regards,
Stennie