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

Retry / warning / default off #300

Open
LindaLawton opened this issue Apr 24, 2024 · 1 comment
Open

Retry / warning / default off #300

LindaLawton opened this issue Apr 24, 2024 · 1 comment
Assignees
Labels
component:python sdk Issue/PR related to Python SDK status:triaged Issue/PR triaged to the corresponding sub-team type:feature request New feature request/enhancement

Comments

@LindaLawton
Copy link

Description of the feature request:

We support retry in this library operations.py#L84

What problem are you trying to solve with this feature?

As of yet it is unclear if we will be billed when we get 500 errors from the api.

This means that retry has the potential of costing a developer a lot of money if it retries without their knowledge.

Any other information you'd like to share?

I would like to suggest that retry be documented disabled by default if its not currently.

And a warning about possible billing issues be added to the readme.

@LindaLawton LindaLawton added component:python sdk Issue/PR related to Python SDK type:feature request New feature request/enhancement labels Apr 24, 2024
@singhniraj08 singhniraj08 added the status:triaged Issue/PR triaged to the corresponding sub-team label Apr 26, 2024
@LindaLawton
Copy link
Author

I got something back from the team that says we will not be charged for 500 and 400 errors. I'm just waiting for it to be documented some place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:python sdk Issue/PR related to Python SDK status:triaged Issue/PR triaged to the corresponding sub-team type:feature request New feature request/enhancement
Projects
None yet
Development

No branches or pull requests

3 participants