@kapa.ai We are running into an issue trying to set up our first connection using Airbyte Cloud. We are trying to set up a connection between HubSpot (source) and Snowflake (destination). It fails in the schema discovery step. Searching about this error code (exit code 137), it seems to be an Out Of Memory problem.

Discovering schema failed
The main container of the DISCOVER operation returned an exit code 137

Your diagnosis is correct: in Airbyte, an exit code 137 during schema discovery typically indicates that the process was killed due to running out of memory (OOM). This is a common issue when the source schema is large or complex, or when the connector requires more resources than are allocated by default. This pattern is confirmed in multiple Airbyte issues and discussions, where exit code 137 is directly linked to OOM situations. The recommended solution is to increase the memory and/or CPU resources allocated to the connector or the relevant Airbyte containers. For example, a core team member explicitly states: “Usually means OOM, please give more memory/cpu to Docker” when exit code 137 is encountered during Airbyte operations [Cluster 'airbyte-abctl' could not be created](https://github.com/airbytehq/airbyte/issues/53691). While most resource adjustment documentation is focused on self-hosted or Kubernetes deployments, the underlying cause and solution are the same for Airbyte Cloud. However, in Airbyte Cloud, you may not have direct control over resource allocation. In this case, you should: - Try reducing the number of streams/tables selected during schema discovery, if possible. - Contact Airbyte Cloud support to request increased memory allocation for your connector, especially if your source (HubSpot) has a large or complex schema. If you continue to encounter this issue, providing Airbyte support with your logs and details about your source schema will help them assist you more effectively. In summary: Exit code 137 during schema discovery in Airbyte Cloud is almost always an out-of-memory issue. The solution is to increase memory resources for the connector, which may require support intervention in Airbyte Cloud [Cluster 'airbyte-abctl' could not be created](https://github.com/airbytehq/airbyte/issues/53691).