2 July 2024

• Internal testing (Shubham thought we had already sent it)
• Wrong email address
• Spike in usage

Send Michael anything useful:

• organizational structure and more about our team
• documentation = H&S options and current plan etc.
• stuff I know it's useful would be great

Plan on how we can monitor proactively Fixes on

1. Api / datastore not accessible sql // this is the case across the whole site // i will test the API (the test example) - there is a server error ; work out why
2. User not able to reset their password
3. 100 spam users were registered

1. Cloudflare issue where we had naming convention issue with all files
   1. This is fixed and deployed etc.
   2. They think that some files were working before but they haven't
2. https://mail.google.com/mail/u/0/#search/___+nhs/FMfcgxwLttGfBwcsKpqZHxsfQHjTMbCP this is still happening for some of their files (## File Download Issue)
3. Increased usage of the ODP
   1. Eg. email thread "## NHSBSA API error" we had to block some IPs
4. Previously, Bigquery was only used for NHS and now it's also used for What to fix
   1. Load on Bigquery and on the servers
5. You had 4 months to test on staging …

Suggestion:

• How we can address this particular request: have confidence in us. in our support
• We should revisit NHS portal and analyze the high peak requests and increase the hardware resources in these periods
• Regarding r2 migration/download, there are no issues currently. They may have occurred during the migration.

Summarize what has happened in the past 2-3 months and share it with me, Meiran and Ismail. We want their confidence. We will be transparent with them re everything we faced. He will send a full email to me

1. Let us explain them why these things are happening the way they are.
2. Have their trust back
   1. Even in terms of support request, monitor a bit in their system at least for some time.. be more proactive in the reliability of their site