Sabbir Ahmmed
03/20/2026, 4:11 PMkapa.ai
03/20/2026, 4:11 PMvalues.yaml Helm chart configuration:
Helm chart V1:
server:
extraEnv:
- name: HTTP_IDLE_TIMEOUT
value: 20m
- name: READ_TIMEOUT
value: 30m
Helm chart V2:
server:
httpIdleTimeout: 20m
extraEnv:
- name: READ_TIMEOUT
value: 30m
[Schema Discovery Timeouts] Additional Notes ⢠If you are running Airbyte behind a load balancer (e.g., on DigitalOcean, AWS, etc.), you may also need to increase the timeout on the load balancer itself, as it may have its own hard timeout independent of Airbyte's configuration. [Review schema 504 timeout]
⢠Some users have reported that even after increasing timeouts, the issue persists ā in those cases, the root cause may be the connector itself taking an unusually long time to fetch the schema (e.g., a large number of objects/tables). [Facebook Marketing timeout]
The knowledge sources don't contain a HubSpot-specific fix, but the timeout configuration above is the standard recommended approach for this class of error across connectors. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.