You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some streams for source-stripe-native are not replicating incrementally despite data being created/updated in Stripe. For example:
ApplicationFees: The incorrect event type is being checked. The connector is checking for application_fee.refunded events when it should be checking for both application_fee.created and application_fee.updated events.
Refunds: No refund events are generated by Stripe. Despite the Stripe API documentation listing refund.created and refund.updated events, these events are not present on the /events endpoint when a refund is created/updated.
Other streams may have these issues too, but they haven't popped up yet or are only checking for a subset of the appropriate events (i.e. only checking for .updated and not .created). It wouldn't be a bad idea to audit all events we're checking & confirm they are actually being created in Stripe. We should also make sure we're checking for all appropriate events for each stream.
A possible solution includes the following:
Checking for different event types between parent streams vs. child streams. Right now, they always check the same event type.
Checking for multiple event types using an array of types as query params (specified like types[0], types[1], etc.) instead of checking for only a single type with the type param.
Switching any streams that don't actually have create/update events over to the existing "no event" resource type.
The text was updated successfully, but these errors were encountered:
Summary
Some streams for
source-stripe-native
are not replicating incrementally despite data being created/updated in Stripe. For example:ApplicationFees
: The incorrect event type is being checked. The connector is checking forapplication_fee.refunded
events when it should be checking for bothapplication_fee.created
andapplication_fee.updated
events.Refunds
: Norefund
events are generated by Stripe. Despite the Stripe API documentation listingrefund.created
andrefund.updated
events, these events are not present on the/events
endpoint when a refund is created/updated.Other streams may have these issues too, but they haven't popped up yet or are only checking for a subset of the appropriate events (i.e. only checking for
.updated
and not.created
). It wouldn't be a bad idea to audit all events we're checking & confirm they are actually being created in Stripe. We should also make sure we're checking for all appropriate events for each stream.A possible solution includes the following:
types[0]
,types[1]
, etc.) instead of checking for only a single type with thetype
param.The text was updated successfully, but these errors were encountered: