Hi @kapa.ai I get this error on open source google search console: Connection pool is full, discarding connection: www.googleapis.com. Connection pool size: 20

This specific “Connection pool is full, discarding connection” warning for

<http://www.googleapis.com|www.googleapis.com>

is not mentioned in the available Google Search Console docs or forum threads, so I can’t point to an official Airbyte-specific fix. The knowledge sources do, however, highlight two related areas you should check: 1. Google Search Console rate limits / QPS If you’re hitting the API very aggressively, you may be exhausting the underlying HTTP client’s connection pool while also approaching Google’s quotas. For Open Source, you can explicitly lower the Search Analytics API Requests Per Minute (or similarly named “API Requests Per Minute” / “Search Analytics API Requests Per Minute”) setting in the Google Search Console source configuration to stay well below your actual quota. Most projects default to 60 RPM even though the documented max is 1200 RPM. [[GSC setup guide](https://docs.airbyte.com/integrations/sources/google-search-console#for-airbyte-open-source); [GSC limits](https://docs.airbyte.com/integrations/sources/google-search-console#limitations--troubleshooting)] 2. Database / Temporal connection pool sizing (indirect but related) Airbyte’s Temporal and database layers use connection pools controlled by

SQL_MAX_CONNS

and

SQL_MAX_IDLE_CONNS

. Misconfigured or too-low values can cause pool exhaustion issues in general. The docs note that Temporal may create multiple pools and effectively use more connections than expected, and that you may need to adjust these values (and the DB’s own

max_connections

) when you see pool-related problems. [[Scaling Airbyte](https://docs.airbyte.com/platform/operator-guides/scaling-airbyte#what-to-scale)] Given what’s documented, the concrete steps you can try are: - In the Google Search Console source config, reduce the “Search Analytics API Requests Per Minute” to something conservative (e.g., 30–40) and re-run the sync. [[GSC setup guide](https://docs.airbyte.com/integrations/sources/google-search-console#for-airbyte-open-source)] - If you’ve customized Airbyte’s DB/Temporal settings, review

SQL_MAX_CONNS

and

SQL_MAX_IDLE_CONNS

and ensure your Postgres

max_connections

is high enough, as undersized pools have previously caused startup/connection issues. [[Scaling Airbyte](https://docs.airbyte.com/platform/operator-guides/scaling-airbyte#what-to-scale)] If, after lowering the per‑minute request setting, you still see the same pool warning and sync failures, the knowledge sources don’t provide further guidance; in that case, capturing the full sync logs and opening a GitHub issue or forum post would be the next step.