@kapa.ai when creating a asynchronous custom connector in the connector builder, is there a limit to the value we can specify for polling job timeout?

Based on the available knowledge sources, there is no documented upper limit on the value you can specify for the Polling Job Timeout in the Connector Builder's asynchronous stream configuration. The documentation describes the

polling_job_timeout

as: > "The time in minutes after which the single Async Job should be considered as Timed Out." and accepts an

integer

or

string

type, with no maximum value mentioned. [YAML Reference] The Polling tab documentation simply advises to "Set an appropriate timeout value (e.g.,

30

for 30 minutes)" without specifying any cap. [Polling Tab Docs] However, there is an important practical caveat: a filed GitHub issue reports that on Airbyte Cloud, even when the Polling Job Timeout is set to a high value (e.g., 2000 minutes), syncs fail with a

SocketTimeoutException

after approximately 5 minutes. This suggests that Airbyte Cloud may enforce an internal platform-level timeout that is independent of — and lower than — the

polling_job_timeout

setting in the Connector Builder. [GitHub Issue #65127] In summary: • No documented limit exists for the

polling_job_timeout

field itself in the Connector Builder. • On Airbyte Cloud, there appears to be an undocumented internal timeout (~5 minutes) that can override your configured value for long-running async jobs. • On self-hosted Airbyte, this platform-level constraint does not appear to apply in the same way. If you are on Airbyte Cloud and experiencing this issue, the knowledge sources do not provide a workaround beyond what is described in the GitHub issue. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.