@Jean-Balteryx (and to anyone else who may not have partner status but might have this same question)
Our support team prefers to handle cases like this individually because there are actually a couple of potential causes of problems that appear similar to indexing problems. Reindexing is not a panacea and should not be attempted unless actually required.
If you run the workflow I attached below and you have records returned via the first or third connector, you can provide those outputs when you contact Support. If you do see records in those outputs, the next step will likely be to back up your MongoDB.
As with all Alteryx Server issues, the response from Support will be most efficient if you supply logs and the version number in your initial contact.
That article is written for internal Alteryx Associates. (I try to remember to check that before I share links with customers, but sometimes I miss one or two.) Because the apparent need to reindex the MongoDB can reflect a few different underlying issues and making any modifications to the MongoDB is to be avoided, we vastly prefer that customers open a case rather than taking such steps on their own. Holders of current, paid licenses can open a case by emailing support@alteryx.com or via the Case Portal. When you open a case, it is fastest if you also include the output of the workflow menitioned attached in my prior comment above, info from Help > About, RuntimeSettings.xml, the current Gallery and Service logs, and screenshots of anyu other behavior that led you to conclude that Reindexing will help. The following articles will guide you in that process:
