@kapa.ai what is this error when trying to setup a new bigquery datasource with a gcs bucekt 2025-12-05 144131,315 [io-executor-thread-6] WARN i.a.c.e.EntitlementServiceImpl(hasEnterpriseConnectorEntitlements-Y0BDzM4):185 - Connector entitlement not available. actorDefinitionId=d2542966-8cc8-4899-9b74-413a7d9bb28e organizationId=OrganizationId(value=00000000-0000-0000-0000-000000000000)

That log line is not a BigQuery or GCS error; it’s coming from Airbyte’s entitlement system:

text Connector entitlement not available.  actorDefinitionId=d2542966-8cc8-4899-9b74-413a7d9bb28e  organizationId=00000000-0000-0000-0000-000000000000

It means the platform checked whether your organization is entitled to use a specific enterprise connector definition (

actorDefinitionId=...

) and found no entitlement. This is informational and related to enterprise/paid connector access, not to BigQuery or GCS connectivity itself. [[Error 500 enterprise](https://github.com/airbytehq/airbyte/issues/53609)] If your BigQuery-with-GCS setup is failing, you’ll need to look for subsequent log entries that mention: -

BigQueryDestination.check

or

BigQueryUtils

- GCS/S3-style errors like

AccessDenied

,

InvalidSecurity

, or schema validation errors for fields such as

gcs_bucket_name

,

gcs_bucket_path

,

credential

, etc. [[BigQuery GCS staging failed](https://discuss.airbyte.io/t/1048); [BQ GCS 403](https://discuss.airbyte.io/t/3806); [GCS schema errors](https://discuss.airbyte.io/t/465)] Those later lines will indicate the real cause (permissions, bucket path, credential format, etc.). The single entitlement warning by itself doesn’t block the connection.