Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Plaid INVALID_PRODUCT errors should not be sent to Sentry #1782

Closed
zachgoll opened this issue Feb 3, 2025 · 0 comments
Closed

Bug: Plaid INVALID_PRODUCT errors should not be sent to Sentry #1782

zachgoll opened this issue Feb 3, 2025 · 0 comments
Labels
Hosted only Hosted app only 3️⃣ Low priority Contributions accepted, but Maybe team will not be working on this in the near term

Comments

@zachgoll
Copy link
Collaborator

zachgoll commented Feb 3, 2025

Currently, we should be protecting against INVALID_PRODUCT errors in Plaid via this line:

def safe_fetch_plaid_data(method)
begin
plaid_provider.send(method, self)
rescue Plaid::ApiError => e
Rails.logger.warn("Error fetching #{method} for item #{id}: #{e.message}")
nil
end
end

That said, there are still errors coming through our Sentry instance indicating that either this is not handling all cases, or we're making an API call elsewhere in the code without proxying through the safe_fetch method.

@zachgoll zachgoll added 3️⃣ Low priority Contributions accepted, but Maybe team will not be working on this in the near term Hosted only Hosted app only labels Feb 3, 2025
@zachgoll zachgoll closed this as completed Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Hosted only Hosted app only 3️⃣ Low priority Contributions accepted, but Maybe team will not be working on this in the near term
Projects
None yet
Development

No branches or pull requests

1 participant