# Recurring DEADLINE\_EXCEEDED after 700s on simple near\_text queries - Shared Cluster GCP Europe

**URL:** <https://forum.weaviate.io/t/recurring-deadline-exceeded-after-700s-on-simple-near-text-queries-shared-cluster-gcp-europe/22207>\
**Category:** Support\
**Tags:** developer-experience, python, technical\
**Created:** [December 31, 2025, 3:55pm UTC](https://forum.weaviate.io/t/recurring-deadline-exceeded-after-700s-on-simple-near-text-queries-shared-cluster-gcp-europe/22207 "2025-12-31T15:55:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mehdi\_Essafi](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/mehdi_essafi/32/3145_2.png) [@Mehdi\_Essafi](https://forum.weaviate.io/u/Mehdi_Essafi)\
**Post date:** [December 31, 2025, 3:55pm UTC](https://forum.weaviate.io/t/recurring-deadline-exceeded-after-700s-on-simple-near-text-queries-shared-cluster-gcp-europe/22207/1 "2025-12-31T15:55:07Z")

</div>

### Environment:

- Weaviate Cloud version: 1.34.5
- Cloud provider: GCP
- Region: Europe
- Cluster type: Shared (99.5% SLA)
- Python client: weaviate-client==4.16.9
- Python: 3.9

* * *

Problem:

Simple near\_text() queries hang for 700+ seconds before failing with DEADLINE\_EXCEEDED. This is happening intermittently on our production cluster.

* * *

Timeline of incident (2025-12-30):

15:41:58 UTC - near\_text() query started  
[NO RESPONSE FOR 12 MINUTES]  
15:53:38 UTC - DEADLINE\_EXCEEDED error

* * *

Python code used:

# Simple vector search - should take \<100ms

response = await collection.query.near\_text(  
query=“CONSEILLER CLIENTÈLE BANCAIRE”,  
limit=10,  
return\_metadata=MetadataQuery(distance=True)  
)

# Simple count - also hangs 700s

result = await collection.aggregate.over\_all(total\_count=True)

* * *

Error log:

grpc.aio.\_call.AioRpcError: \<AioRpcError of RPC that terminated with:  
status = StatusCode.DEADLINE\_EXCEEDED  
details = “Deadline Exceeded”  
debug\_error\_string = “UNKNOWN:Error received from peer {grpc\_status:4, grpc\_message:“Deadline Exceeded”}”

> 

weaviate.exceptions.WeaviateQueryError: Query call with protocol GRPC search failed with message Deadline Exceeded.

After the initial failure, subsequent queries fail with:  
status = StatusCode.UNAVAILABLE  
details = “recvmsg:Connection timed out”

* * *

Collection sizes:

- StaticRole: ~few thousand objects
- Skill: ~18,800 objects
- JobTitle: ~few thousand objects

* * *

Questions:

1. Is this expected behavior on Shared tier during high-traffic periods?
2. Are there known issues with GCP Europe region or v1.34.5?
3. What timeout configuration do you recommend for Shared clusters?
4. Should we implement specific retry/circuit-breaker patterns?

---

<div class="post-metadata">

**Author:** ![Shahin](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/shahin/32/8085_2.png) [@Shahin](https://forum.weaviate.io/u/Shahin)\
**Post date:** [December 31, 2025, 3:57pm UTC](https://forum.weaviate.io/t/recurring-deadline-exceeded-after-700s-on-simple-near-text-queries-shared-cluster-gcp-europe/22207/2 "2025-12-31T15:57:22Z")

</div>

**Hi** @Mehdi_Essafi

I’ve received your ticket on [support@weaviate.io](mailto:support@weaviate.io) and have responded to you there.

As you’re a customer on our cloud platform, please use [support@weaviate.io](mailto:support@weaviate.io) for future support requests. This will allow you to open a ticket in our system and access your cloud clusters more efficiently, ensuring a faster resolution.

Best regards,  
Mohamed Shahin  
Weaviate Support Engineer