Hi I am using cloud version of airbyte and I am facing data issues. First sync works fine but subsequent syncs push junk data or bad data to my destinations. For example i am using stripe to S3 connection, in subsequent syncs i am getting invoice object in invoice line item streams, another issue i faced is in first sync i got a invoice id in charge, but in later sync same charge sent even though there were no updates in stripe but airbyte pulled the data inspite of being having a cursor as updated, and that too with wrong data that is same charge was not having any transaction id.

You’re running into two known classes of issues: 1. Stripe

invoice_line_items

containing invoice objects instead of line items This matches a recently reported regression in the Stripe source connector (v5.11.0), where

invoice_line_items

started returning invoice-level data (invoice id and missing line-item fields) instead of proper line items. [[Stripe issue](https://github.com/airbytehq/airbyte/issues/59154)] The root cause was identified and fixed in a later Stripe connector release (5.12.0). [[Stripe fix](https://github.com/airbytehq/airbyte/issues/59154)] Action: - In Airbyte Cloud, check the version of your Stripe source. - If it’s 5.11.0 (or an affected version), upgrade to the latest available Stripe connector version and re-run the sync. - You will likely need to reset the affected streams (at least

invoice_line_items

) so they are re-synced with the corrected behavior. 2. Incremental syncs re-sending unchanged records / “junk” or duplicate data There are a few relevant points from the docs and forum: - Incremental syncs rely on a cursor and state; records with cursor values

<=

the stored cursor are considered already synced, and only records with cursor

>

that value should be pulled next time. [[Incremental syncs](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/incremental-syncs)] - For Stripe, incremental behavior is more complex because the Stripe API doesn’t natively support “updated since last sync” for all objects. Airbyte uses: - The Events API where possible, to approximate “updated” behavior. [[Stripe troubleshooting](https://docs.airbyte.com/integrations/sources/stripe#troubleshooting)] - For many streams (including

Charges

,

Invoice Line Items

,

Invoices

, etc.), an artificial

updated

cursor field managed by Airbyte. [[Stripe troubleshooting](https://docs.airbyte.com/integrations/sources/stripe#troubleshooting)] - There have been known incremental issues and fixes in Stripe streams (e.g., duplicates, incorrect incremental behavior) that required connector upgrades and sometimes a full reset. [[Stripe migration 5.0.0](https://docs.airbyte.com/integrations/sources/stripe-migrations#upgrading-to-500)] Your symptoms: - Same charge re-sent on later syncs despite no Stripe changes This is consistent with incremental bugs that have been reported (e.g., records being re-sent even when using an

updated

cursor). [[Incremental issues forum](https://discuss.airbyte.io/t/504); [Stripe incremental issues](https://docs.airbyte.com/integrations/sources/stripe-migrations#upgrading-to-500)] - Charge losing fields (e.g., transaction id missing on later sync) The knowledge sources confirm schema and transformation issues have occurred around Stripe updates, but they don’t give a specific root cause for missing fields in

charges

. [[Stripe migration 5.0.0](https://docs.airbyte.com/integrations/sources/stripe-migrations#upgrading-to-500)] I’m sorry, but there’s no explicit documentation in the provided sources about this exact “transaction id disappears on later syncs” behavior. Actions to take: 1. Confirm connector version and upgrade - In Airbyte Cloud, open your Stripe source and check the version. - Upgrade to the latest Stripe connector version (this includes multiple incremental and schema fixes, including the

invoice_line_items

regression). [[Stripe fix](https://github.com/airbytehq/airbyte/issues/59154); [Stripe migration 5.0.0](https://docs.airbyte.com/integrations/sources/stripe-migrations#upgrading-to-500)] 2. Reset and re-sync affected streams - For streams with clearly bad data (

invoice_line_items

, possibly

charges

,

invoices

), perform a “Reset data” on those connections/streams and then run a fresh sync so state and cursor are rebuilt from scratch. [[Stripe migration 5.0.0](https://docs.airbyte.com/integrations/sources/stripe-migrations#upgrading-to-500)] 3. Check your sync mode and cursor configuration - Ensure the streams are set to Incremental with the default cursor (

updated

or the documented cursor for that stream) and that the destination mode (e.g., S3) is what you expect (Append vs Overwrite). [[Stripe troubleshooting](https://docs.airbyte.com/integrations/sources/stripe#troubleshooting); [Incremental syncs](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/incremental-syncs)] 4. If issues persist, open a support ticket / GitHub issue - Include: - Source connector version - Connection ID - Example record IDs (e.g., specific charge id, invoice id) - Job logs for a “good” first sync and a “bad” subsequent sync - Similar issues have been investigated and fixed via GitHub issues before. [[Stripe issue](https://github.com/airbytehq/airbyte/issues/59154)] If you share your Stripe source version and which exact streams are misbehaving (charges, invoices, invoice_line_items, others), I can help you narrow down which known fixes apply and what to reset.

i am already using the stripe connector version 5.15.14 @kapa.ai

A message from kapa.ai