From edad1c9a215ef6bb237801e9b383b1c9304e967d Mon Sep 17 00:00:00 2001
From: David McDonald <david.mcdonald@digital.cabinet-office.gov.uk>
Date: Fri, 24 Dec 2021 08:56:42 +0000
Subject: [PATCH] Bump sqlalchemy statement timeout even higher for reporting
 worker

We saw it fail again last night to calculate how many notifications
were sent for one of our services to put in the ft_notification_status
table. It ran in to the sqlalchemy statement timeout again.
To get us through the holiday
period lets make it 2 hours as surely that will be enough and then
we can fix this properly
---
 manifest.yml.j2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manifest.yml.j2 b/manifest.yml.j2
index 09c0a5551..ee633402f 100644
--- a/manifest.yml.j2
+++ b/manifest.yml.j2
@@ -58,7 +58,7 @@
     'additional_env_vars': {
       'CELERYD_MAX_TASKS_PER_CHILD': 1,
       'CELERYD_PREFETCH_MULTIPLIER': 1,
-      'SQLALCHEMY_STATEMENT_TIMEOUT': 2400
+      'SQLALCHEMY_STATEMENT_TIMEOUT': 7200
     }
   },
   'notify-delivery-worker-priority': {},