Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Endless 'Error persisting data to Stitch: 400' error #43

Open
willyhum opened this issue Apr 24, 2021 · 2 comments
Open

Endless 'Error persisting data to Stitch: 400' error #43

willyhum opened this issue Apr 24, 2021 · 2 comments

Comments

@willyhum
Copy link

willyhum commented Apr 24, 2021

Hey everyone

I'm getting this 400 error on all extractions:

Error persisting data to Stitch: 400: {'error': 'Record 130 for table payment_sources did not conform to schema:\n#: #: no subschema matched out of the total 2 subschemas\n#: expected: null, found: JSONObject\n#/reference_id: #: no subschema matched out of the total 2 subschemas\n#/reference_id: expected: null, found: String\n#/reference_id: expected maxLength: 50, actual: 52\n'}

In the logs themselves im getting:

2021-04-24 04:30:34,093Z tap - WARNING Removed paths list: ['billing_address.object', 'billing_address.validation_status', 'cf_guid', 'cf_is_migrated', 'cf_password_hash', 'cf_verified', 'payment_method.gateway_account_id']

2021-04-24 04:30:34,114Z tap - WARNING Removed paths list: ['dunning_attempts', 'line_item_taxes.0.object', 'line_item_taxes.1.object', 'line_items.0.customer_id', 'line_items.1.customer_id', 'shipping_address.object', 'shipping_address.validation_status', 'taxes.0.object']

And lots more of the same error just with different attributes.

Setup is CB-Singer/Stitch-BigQuery

I tried to set up a second connection and create new tables fresh, but the same error persists even with a clean setup.

Updated: Could it be related to this (singer-io/tap-xero#17)

@NachoJusticia
Copy link

I am getting the same warning and don't know how to fix it:

WARNING Removed paths list: ['cancel_schedule_created_at', 'cf_custom_name']
WARNING Removed 2 paths during transforms:
	cancel_schedule_created_at
	cf_custom_name

@NachoJusticia
Copy link

I think the problem is that those fields are chargebee custom fields, and they don't appear in catalog.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants