@kapa.ai, getting error getting error Discovering schema failed The discover catalog failed due to an internal error for source: d144867e-7558-4499-bf91-2cbb5ec95c45

The "Discovering schema failed" error in Airbyte can have several causes. Here are the most common ones and potential solutions: Common Causes & Solutions 1. Large Number of Tables/Streams (413 Request Entity Too Large) If your source has a very large number of tables (e.g., 10,000+), the catalog response can exceed the server's request size limit. [source-mssql 413 error] For Kubernetes/Helm deployments, you can try increasing limits via a `values.yaml`:

global:
  env_vars:
    MICRONAUT_SERVER_MAX_REQUEST_SIZE: "104857600" # 100MB

webapp:
  ingress:
    annotations:
      nginx.ingress.kubernetes.io/proxy-body-size: "50m"

2. Out of Memory (Exit Code 137) If the connector runs out of memory during discovery, it will fail with exit code 137. This can happen with sources that have a large number of entities to discover. [source-microsoft-dataverse OOM] 3. Schema/Configuration Issues • Too many schemas selected: Try limiting the source to a specific schema (e.g., only the

public

schema for Postgres). [Postgres schema detection failure] • Incremental loading settings: Some custom connectors fail discovery when incremental sync is configured. Try disabling incremental settings to see if discovery succeeds. [custom connector issue] • Primary key misconfiguration: A primary key defined in the connector that doesn't exist in the schema can cause discovery to fail. [schema discovery issue] 4. Outdated Airbyte or Connector Version Upgrading Airbyte or the connector version has resolved discovery failures for many users. [schema discovery issue] Recommended Troubleshooting Steps 1. Check the logs in the Airbyte UI for more specific error details (e.g., 413, 504, exit code 137). 2. Reduce the scope of your source (fewer schemas, tables, or property IDs). 3. Upgrade your Airbyte platform and connector to the latest versions. 4. Check your connector configuration for any mismatches (e.g., primary keys, incremental settings). Could you share more details about your source connector type and any additional log output? That would help narrow down the specific cause. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.