@kapa.ai i am building a custome connector for Facebook market. when i try to connect new source on my local env, the airbyte returns 500 error. why?

There are a few known reasons why you might get a 500 error when connecting a custom Facebook Marketing source connector locally. Based on the knowledge sources, here are the most likely causes: 1. Missing or Invalid Schema in Connector Manifest When using the low-code connector builder, if your connector manifest doesn't include an inline schema, Airbyte may throw a

NullPointerException

when trying to validate the catalog. One user resolved this by adding the schema inline in the connector manifest YAML instead of relying on the default JSON schema loader. [500 Error Forum Post] 2. Version Bug in Local Deployment A known bug in certain Airbyte versions (e.g.,

1.7.0

) causes 500 errors when creating or configuring connectors locally. A reported workaround is to downgrade to chart version

1.6.3

:

abctl local install --chart-version 1.6.3

You can check available versions at ArtifactHub. [403/500 Error GitHub Issue] 3. Cache Problem on the Airbyte Server In some cases, a 500 error on

list_enterprise_source_stubs

is caused by a server cache issue. Restarting the

airbyte-server

container can resolve it. [HTTP 500 GitHub Issue] 4. Facebook API-Specific Issues If the connector is already set up and the error occurs during sync (not setup), it could be due to: • Invalid OAuth scopes (e.g.,

read_insights

is deprecated and rejected by Meta). [OAuth Scope Issue] • Too many fields requested from the Facebook Graph API. [Fields Error Issue] Recommended steps: 1. Check if adding an inline schema to your connector YAML resolves the issue. 2. Verify your Airbyte version and try downgrading if needed. 3. Restart the

airbyte-server

container to clear any cache. 4. Review your connector's OAuth scopes and ensure they are valid. If none of these help, consider filing a bug report on Airbyte's GitHub with your connector YAML and server logs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.