tconbeer
commented
4 years ago I had the same error.
I think the root cause is that our Chargebee account doesn't have orders enabled, which is causing the API call to fail. Transactions, Subscriptions, Plans, and other models follow Orders alphabetically, and so are extracted after Orders in Stitch; the error on Orders prevents the other models from syncing.
After I deselected the orders table from the "Tables to Replicate" section in the Stitch settings, the other models synced fine.
As a solution, either: 1) The error should cause an exception that Stitch can raise as a notification, or 2) This tap should catch and handle these errors from the API so the other tables aren't affected
BrianMinhTruong
chandrasen-rajashekar
luandy64
We've been successful with Customers and Invoices, but the three schema's above aren't working. Get the following error for Orders, unsure if the same error is impacting subscriptions and transactions: tap - ERROR 400 Client Error: Bad Request for url: https://acloudguru-us.chargebee.com/api/v2/orders?include_deleted=True&limit=100&updated_at%5Bafter%5D=1532822400
Looks like others aren't getting populated because the tap process stops after this error and exits out.
Worth noting I'm coming from the Stitch Beta if that helps.