@kapa.ai my airbyte terraform has this error . I am not specifying any specific field i want to seelect all fields from the table

error: failure to invoke API: unknown status code returned: Status 400
    {"status":400,"type":"<https://reference.airbyte.com/reference/errors#bad-request>","title":"bad-request","detail":"The request could not be understood by the server due to malformed syntax.","documentationUrl":null,"data":{"message":"Invalid fields selected for stream Integration. The list of valid field names includes: [updated_at, oauth_scopes, _ab_cdc_updated_at, created_at, description, provider_id, _ab_cdc_deleted_at, _ab_cdc_lsn, id, type, deleted_at]."}}

The error message you're seeing is: > "Invalid fields selected for stream Integration. The list of valid field names includes: [updated_at, oauth_scopes, _ab_cdc_updated_at, created_at, description, provider_id, _ab_cdc_deleted_at, _ab_cdc_lsn, id, type, deleted_at]." This is a field selection validation error from the Airbyte API. Even though you intend to select all fields, your Terraform configuration is likely passing an explicit

selectedFields

list that contains one or more field names that don't exist in the stream's schema. Based on what the knowledge sources describe about field selection [Select Fields]: • By default, Airbyte syncs all detected fields from the source — you don't need to specify any

selectedFields

at all to get all fields. • When you do specify

selectedFields

, every field in that list must be a valid field name for that stream. What to check in your Terraform config: 1. Remove the

selectedFields

block entirely if you want all fields. Not specifying it will cause Airbyte to sync all fields by default. 2. If you must specify fields, ensure every field name exactly matches one of the valid names listed in the error:

updated_at

,

oauth_scopes

,

_ab_cdc_updated_at

,

created_at

,

description

,

provider_id

,

_ab_cdc_deleted_at

,

_ab_cdc_lsn

,

id

,

type

,

deleted_at

. A similar issue was reported with the Salesforce connector where specifying a cursor field not included in

selectedFields

caused a 400 error [source-salesforce issue] — the root cause is the same: the API rejects requests when the provided field list doesn't match the stream's valid schema. The knowledge sources don't contain specific Terraform provider documentation, so I can't show you the exact Terraform syntax to fix this, but the resolution is to either omit the field selection entirely or correct the field names to match the valid list provided in the error. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

i didnt include

selectedFields

If you're not including

selectedFields

at all, the knowledge sources don't provide enough detail to pinpoint the exact cause of this specific 400 error in your Terraform configuration. However, a few things worth checking based on what the knowledge sources do cover: 1. Cursor field validation: If you're using an incremental sync mode and specifying a

cursorField

, the API can return a 400 if the cursor field isn't properly recognized. A similar issue was documented where specifying certain cursor fields caused a 400 bad request [source-salesforce issue]. 2. Other stream configuration fields: The error may be triggered by another part of your stream configuration (e.g.,

syncMode

,

primaryKey

, or

cursorField

) referencing a field name that doesn't match the stream's valid schema. Could you share the relevant portion of your Terraform

configurations.streams

block? That would help narrow down which part of the configuration is causing the API to reject the request. The valid field names for the

Integration

stream, as listed in the error, are: •

updated_at

,

oauth_scopes

,

_ab_cdc_updated_at

,

created_at

,

description

,

provider_id

,

_ab_cdc_deleted_at

,

_ab_cdc_lsn

,

id

,

type

,

deleted_at

So if any of your other stream settings (like

cursorField

or

primaryKey

) reference a field name not in that list, that could be the cause. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.