https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> how can I configure source connecto...
# replication-ask-ai
k
@kapa.ai how can I configure source connector test timeouts. My google ads times out at 30 seconds
k
You can increase the connector test timeouts via the connector’s acceptance-test configuration, not inside the Google Ads connector itself. For the standard connector tests: - Connection test timeout is controlled by 
acceptance_tests.connection.tests.timeout_seconds
. Default is 30 seconds.[[Test connection](https://docs.airbyte.com/platform/connector-development/testing-connectors/connector-acceptance-tests-reference#test-connection)] - Discovery test timeout is controlled by 
acceptance_tests.discovery.tests.timeout_seconds
. Default is 30 seconds.[[Test discovery](https://docs.airbyte.com/platform/connector-development/testing-connectors/connector-acceptance-tests-reference#test-discovery)] In your connector’s 
acceptance-test-config.yml
, you can raise these, for example:
Copy code
yaml acceptance_tests:   connection:     tests:       - config_path: "secrets/config.json"         status: "succeed"         timeout_seconds: 600  # 10 minutes   discovery:     tests:       - config_path: "secrets/config.json"         timeout_seconds: 600  # 10 minutes
This will prevent the acceptance tests from failing at 30 seconds when running against slower sources like Google Ads. For runtime sync timeouts of the Google Ads connector itself (e.g., 
shopping_performance_view
timing out), the linked GitHub issue discusses experimenting with longer timeouts and smaller 
slice_duration
, and suggests making these configurable, but there is no documented, user-facing configuration option yet.[[Google Ads issue](https://github.com/airbytehq/airbyte/issues/49254)]
k
@kapa.ai where do I put this in my help deployment
k
A message from kapa.ai
In a Helm/Kubernetes deployment, you don’t configure connector test timeouts via the Helm `values.yaml`; they are set in the connector’s 
acceptance-test-config.yml
 file used when running connector acceptance tests. The docs only describe: - How to build a 
values.yaml
override for deploying Airbyte (platform-level config like 
global.airbyteUrl
, server timeouts, etc.).[[Create values.yaml](https://docs.airbyte.com/platform/deploying-airbyte#3-create-a-valuesyaml-override-file)] - How to increase schema discovery HTTP timeouts at the server level via 
values.yaml
, e.g.:[[Schema discovery timeouts](https://docs.airbyte.com/platform/enterprise-setup/scaling-airbyte#schema-discovery-timeouts)]
Copy code
yaml server:   extraEnv:     - name: HTTP_IDLE_TIMEOUT       value: 20m     - name: READ_TIMEOUT       value: 30m
or for Helm v2:
Copy code
yaml server:   httpIdleTimeout: 20m   extraEnv:     - name: READ_TIMEOUT       value: 30m
There is no documentation indicating that 
acceptance_tests.*.timeout_seconds
can be set via Helm values; it must live in the connector repo’s 
acceptance-test-config.yml
(used when you run connector acceptance tests), not in your Helm deployment files.[[Test connection](https://docs.airbyte.com/platform/connector-development/testing-connectors/connector-acceptance-tests-reference#test-connection); [Test discovery](https://docs.airbyte.com/platform/connector-development/testing-connectors/connector-acceptance-tests-reference#test-discovery)] If your issue is the platform’s HTTP timeout during discovery or connection checks in the UI, you can only adjust the server timeouts in 
values.yaml
as shown above; beyond that, the knowledge sources do not document a way to tune per-connector test timeouts through Helm.
4 Views
Open in Slack
PreviousNext
Powered by