Closed leobarcellos closed 3 months ago
Appreciate the find! In general we've stopped using the SQS driver for queues because of how many odd restrictions it has and have considered removing it from the codebase before. If you are actively using it please let us know if you run into any other oddities!
Appreciate the find! In general we've stopped using the SQS driver for queues because of how many odd restrictions it has and have considered removing it from the codebase before. If you are actively using it please let us know if you run into any other oddities!
Alright! I actually thought that with SQS it would be easier to scale and reduce the risk of "losing the message" if anything goes wrong. I thought that using redis might somehow lose it when scaling -- But it was just assumption.
I will keep monitoring and for sure report it if I run into any weirdness
This fixes the Message SQS Queue Provider. "DelaySeconds" was being sent in milliseconds, however AWS SQS accepts seconds (and 900 is the maximum).
Screenshot of the error from worker below: