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

Add retry logic (and delays?) to our task handling #14

Open
rsyring opened this issue Jun 20, 2024 · 0 comments
Open

Add retry logic (and delays?) to our task handling #14

rsyring opened this issue Jun 20, 2024 · 0 comments

Comments

@rsyring
Copy link
Member

rsyring commented Jun 20, 2024

See:

We'd have to put the retry config into the task invocation event and then handle it ourselves. We could handle short (<10s?, <1m?) retry delays by sleeping. By sleeping we pay for the execution time. So we'd probably only want to use this method for quick retries like a failed network/db connection.

If we want a longer delay, we'd need to put a message in an sqs queue with a timer. Max delay on that is only 15 mins. No obvious way to do a longer delay (hours) like we can do with Celery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant