Check the database path in the URI
A MongoDB connection URI contains a host and may include a database name after the slash, such as `mongodb+srv://host.example/mydb`. That path selects the database used for operations. If you save a URI without a database path, the SDK falls back to the documented `iagenify_db` name rather than guessing which database you intended.
This can make a successful connection look like a missing-data problem. The server may be reachable and authentication may work, while a `collections` or `find` operation reads from a different database than the one where your records live. Confirm the intended database name with the database administrator before changing the URI.
Verify the target before querying or writing
Update the saved connection with the URI containing the correct database path, keeping the secret in the protected credentials field. Then run a read-only operation such as listing collections or checking a known record. Confirm the selected connection and database before starting inserts, updates, or a workflow that changes data.
Do not paste a full URI into a support request because it may contain a password. Share the provider, sanitized host, intended database name, operation, and error instead. If the database still appears empty after selecting the correct name, check the account's database permissions and whether the expected records are present in that exact database.