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
SQS backoff_policy no longer works #1824
Comments
Looked again, and this assertion isn't true - I've misread the code. Not entirely sure why I'm getting this error (only when setting |
can you help to reproduce with celery 5.3.6? |
Same behaviour with Celery 5.3.6. However, I think this is my misunderstanding of the documentation - So, my solution at least is to NOT use The Celery SQS documentation is pretty unclear on all this (as is the documentation of the More appropriate behaviour, I would think, would be to ignore |
Versions:
Using
acks_late
Setting
backoff_policy
fails with aKeyError
when a message fails:From what I can see of the Kombu SQS implementation calls to boto3
receive_message
andreceive_messages
don't request any attributes (noAttributeNames
parameter). At least in my experiments,receive_message
andreceive_messages
don't returnAttributes
unless specifically requested to do so.Not sure if this is a change in Kombu or boto
The text was updated successfully, but these errors were encountered: