Leo Hemsted 0088bcd98b only retry if the broadcast message task is in sending ...

previously we would retry if the task was queued up for retry but the
status is in "received-ack" or "received-err". We don't expect that a
task will be retried after getting this status, but if there are
duplicate tasks that could happen. Lets plan for the worst by saying
"only process a retry if the task is currently in sending".

this way, if a duplicate task is on retry and the first task goes
through succesfully, the duplicate task will give up.

2021-02-18 12:03:36 +00:00

..

__init__.py

…

broadcast_message_tasks.py

only retry if the broadcast message task is in sending

2021-02-18 12:03:36 +00:00

celery.py

…

letters_pdf_tasks.py

Remove redundant (renamed) letters task

2021-02-17 12:57:50 +00:00

nightly_tasks.py

Alert on 2nd class letters still in sending everyday

2021-01-13 11:21:27 +00:00

process_ses_receipts_tasks.py

…

process_sms_client_response_tasks.py

…

provider_tasks.py

Downgrade exception to warning for provider API call

2021-01-18 17:00:21 +00:00

reporting_tasks.py

…

research_mode_tasks.py

…

scheduled_tasks.py

Fix linting errors

2021-02-16 09:03:38 +00:00

service_callback_tasks.py

Put service callback retries on a different queue

2021-02-09 13:31:16 +00:00

tasks.py

Use cache for tasks that save notifications

2021-01-18 10:25:24 +00:00