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

RetryConfig seems to be ignored on @tasks_fn.on_task_dispatched #177

Open
sjudd opened this issue Feb 14, 2024 · 3 comments
Open

RetryConfig seems to be ignored on @tasks_fn.on_task_dispatched #177

sjudd opened this issue Feb 14, 2024 · 3 comments
Labels
waiting for customer response Issue is on hold awaiting more information from OP

Comments

@sjudd
Copy link

sjudd commented Feb 14, 2024

I created a task queue function and configured the try config using the decorator:

@tasks_fn.on_task_dispatched(
    secrets=["SOME_SECRET"],
    retry_config=RetryConfig(max_attempts=5, min_backoff_seconds=60),
    rate_limits=RateLimits(max_concurrent_dispatches=1),
)

But when the body of the function throws an Error, I see 15 retries spaced about 10 seconds apart:

image

I'd expect to see only 5 retries. I'd expect each one to be at least a minute apart.

I'd also expect to see some kind of exponential backoff behavior, but instead the time between retries seems fixed

@exaby73
Copy link
Contributor

exaby73 commented Mar 4, 2024

Hey @sjudd. Could you give me the logs for one of these errors?

@exaby73 exaby73 added the waiting for customer response Issue is on hold awaiting more information from OP label Mar 4, 2024
@sjudd
Copy link
Author

sjudd commented Sep 19, 2024

@exaby73 sorry i missed this. Can you clarify what you're looking for? The error is an incorrectly formatted request to a graphql endpoint.

@exaby73
Copy link
Contributor

exaby73 commented Oct 16, 2024

Can you expand the error and paste one here with any private information redacted?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for customer response Issue is on hold awaiting more information from OP
Projects
None yet
Development

No branches or pull requests

2 participants