@kapa.ai i am seeing errors in temporal like "

List query exceeded threshold

"

The knowledge sources don’t mention the specific Temporal error message

List query exceeded threshold

, so I can’t give a precise, documented root cause or fix for that exact string. However, there are a few relevant points about Temporal-related errors in Airbyte: - Airbyte’s Temporal service is sensitive to latency and timeouts when talking to its PostgreSQL database; networking or DB performance issues can surface as Temporal errors. In one EKS deployment, moving the Temporal DB (Postgres/RDS) into the same region/closer to the EKS cluster resolved persistent Temporal “context deadline exceeded” issues and made the system stable again.[[Temporal EKS issue](https://github.com/airbytehq/airbyte/issues/59730)] - Another documented Temporal error (

io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED

) has been mitigated in practice by increasing server resources (CPU/memory/disk) and restarting Airbyte, suggesting that resource pressure can trigger Temporal-side failures.[[DEADLINE_EXCEEDED forum](https://discuss.airbyte.io/t/254)] Given that: 1. Check Temporal’s Postgres: - Ensure the Temporal DB is in the same region / low-latency network as the Airbyte deployment. - Verify DB CPU/IO load and that it’s not under-provisioned. 2. Check cluster / host resources: - Increase CPU and memory for the Temporal pod (or the whole Airbyte instance) and restart. 3. Look at full Temporal logs: - The surrounding stack trace or error context may show whether this is a DB query limit/timeout or an internal Temporal list operation hitting a threshold. Because the sources don’t document

List query exceeded threshold

specifically, if these checks don’t help, I’d recommend opening an issue or forum topic and attaching your Temporal logs so the Airbyte team can correlate it with known Temporal behavior.