Transactions/Subscriptions/Orders Data not coming through

[zacharydcooper]

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.

[tconbeer]

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]

Thanks @tconbeer! I just disabled orders from our Tables to Replicate, and now subscriptions and transactions are coming through.

[chandrasen-rajashekar]

Hi, I have been using Chargebee integration since quite sometime and currently even though I do not see any error the data in subscription table seems to be not updating since last 2 days. Does anyone facing the same problem currently?

[luandy64]

Maybe the issues with Orders is related to / solved by #25?