Creating an Airbyte connection via Terraform times out with HttpTimeoutException

TL;DR

For "HttpTimeoutException": the fix was released in Airbyte platform v0.50.31, which raised the timeout defaults and changed the API server's thread allocation. Airbyte fixed this server-side in platform v0.50.31, which raised the timeout defaults and adjusted how the API server allocates threads.

HttpTimeoutException

Steps

1. The Terraform provider's API call was timing out because the server's default timeouts and thread allocation couldn't keep up with connection creation. Airbyte fixed this server-side in platform v0.50.31, which raised the timeout defaults and adjusted how the API server allocates threads. Fix: upgrade your Airbyte instance to v0.50.31 or later and re-run the Terraform apply. The connection creation should finish within the call instead of timing out. Source: https://github.com/airbytehq/airbyte/issues/29506

When to use

You are seeing this: Creating an Airbyte connection through the Terraform provider consistently failed with an HttpTimeoutException after 120 seconds. Use this skill when you run into "Creating an Airbyte connection via Terraform times out with HttpTimeoutException".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: platform v0.50.31. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/airbytehq/airbyte/issues/29506

In the thread https://vectle.com/threads/thrtewgGYuS20MmV17WwNPNA, the question was: Creating an Airbyte connection through the Terraform provider consistently failed with an HttpTimeoutException after 120 seconds. The sync completed on the server side, but the API call timed out, so Terraform reported a failure. An Airbyte maintainer acknowledged the default request and timeout settings were too low for the connection-creation path. The fix was released in Airbyte platform v0.50.31, which raised the timeout defaults and changed the API server's thread allocation. The maintainer confirmed the fix landed in that release and asked users to re-run their plans on the new version. The verified resolution was: The Terraform provider's API call was timing out because the server's default timeouts and thread allocation couldn't keep up with connection creation. Airbyte fixed this server-side in platform v0.50.31, which raised the timeout defaults and adjusted how the API server allocates threads. Fix: upgrade your Airbyte instance to v0.50.31 or later and re-run the Terraform apply. The connection creation should finish within the call instead of timing out. Source: https://github.com/airbytehq/airbyte/issues/29506