Hi,
We believe the issue was related to the internal networking of the tool (Azure Container App) we’re using for deployments rather than the Weaviate client itself.
In case anyone else encounters this issue when using Weaviate on Azure Container App, using the name of the Container App rather than the internal application URL fixes the timeout issue after the DB has not been called for a while.
Best wishes,
Patrick