Community

Connector Improvement: Stripe connector generates noisy warnings if Stripe feature not enabled

Dean Verhey User

August 30, 2022 21:06
Edited

We don't use Stripe's issuing APIs and don't have it enabled for our Stripe account (or selected for sync in Fivetran), but we noticed that Fivetran is still pinging issuing-related Stripe endpoints, generating some noise in our Stripe logs on every Fivetran sync.

{
  "error": {
    "message": "Your account is not set up to use Issuing. Please visit https://dashboard.stripe.com/issuing/overview to get started.",
    "type": "invalid_request_error"
  }
}

This shows in the Fivetran dashboard with a "Tables Excluded: We couldn't sync the following tables because of the Stripe errors below: We do not have required permissions to access this table" alert, but in reality there's no error - we just don't use that Stripe functionality.

It would be appreciated if Fivetran could do its permission checks in a way that doesn't ping the endpoints themselves, perhaps avoiding this noise in both Fivetran and (more importantly for us) our Stripe logs.

Please sign in to leave a comment.

Comments

2 comments

Fiona Cober User
- October 31, 2022 13:28
I'm experiencing the same thing, we're getting a lot of errors in our Stripe dashboard from Fivetran still trying the API endpoints of features we don't have (even though the relevant tables are all turned off from syncing in the schema). It makes it challenging for us to see real errors we need to be concerned about.
Guillaume Pelletier User
- May 07, 2024 20:49
Fivetran is apparently doing this intentionally just so they can grey out some tables and add contextual tooltips. It's a nice gesture, but I don't understand why Fivetran thinks that doing this is more important than to avoid trying to access resources it has been denied. This is especially true of Stripe data, which is inherently sensitive, for what I think should be obvious reasons.

Fiona Cober User

October 31, 2022 13:28

I'm experiencing the same thing, we're getting a lot of errors in our Stripe dashboard from Fivetran still trying the API endpoints of features we don't have (even though the relevant tables are all turned off from syncing in the schema). It makes it challenging for us to see real errors we need to be concerned about.

Guillaume Pelletier User

May 07, 2024 20:49

Fivetran is apparently doing this intentionally just so they can grey out some tables and add contextual tooltips. It's a nice gesture, but I don't understand why Fivetran thinks that doing this is more important than to avoid trying to access resources it has been denied. This is especially true of Stripe data, which is inherently sensitive, for what I think should be obvious reasons.