[Chargebee] Add has_scheduled_changes filter to subscription_with_scheduled_changes stream

[lukewatters-airbyte]

Problem
The subscription_with_scheduled_changes stream currently fetches the entire subscriptions dataset on every sync and filters records on the client side. For users with large Chargebee accounts, this results in very long sync times — in some cases over 2 hours for this stream alone, while other streams in the same connector complete in under 30 minutes.

Proposed Solution
The Chargebee API supports a has_scheduled_changes=true query parameter on the list subscriptions endpoint. Applying this filter server-side when syncing the subscription_with_scheduled_changes stream would mean only relevant records are fetched, significantly reducing sync duration and the number of API calls made.
API reference: https://apidocs.eu.chargebee.com/docs/api/subscriptions?lang=python-v2#list_subscriptions_has_scheduled_changes

Who benefits
Any Airbyte user syncing Chargebee data with the subscription_with_scheduled_changes stream, particularly those with large subscription volumes where the current full-refresh approach causes excessive sync times and high API request load.

[airbyte-support-bot]

Hi lukewatters-airbyte, thank you for this well-documented feature request!

Your analysis is spot on. Looking at the current connector implementation, the subscription_with_scheduled_changes stream uses a substream pattern that:

1. Fetches all subscriptions from the parent subscription stream
2. Calls GET /subscriptions/{id}/retrieve_with_scheduled_changes for each subscription individually
3. Ignores 400/404 errors for subscriptions that have no scheduled changes

This means for a Chargebee account with, say, 50,000 subscriptions but only 100 with scheduled changes, the connector still makes 50,000+ API calls — one per subscription — and discards the vast majority of responses. Adding has_scheduled_changes=true as a server-side filter on the parent subscription query would dramatically reduce both API calls and sync time by only iterating over relevant subscriptions.

This has been escalated to the internal team for review. I'll update this thread once there's a tracking issue linked.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

[airbyte-support-bot]

This issue is being tracked internally: https://github.com/airbytehq/oncall/issues/11913