Since Monday 20th April, we have been observing elevated levels in production of A&G Conversion returning 422s with a null response body. Could this correlation ID be looked into please?
An example correlation ID is d4720188-1272-4b6a-b9a9-91aa9c227fbd.
Thank you
Hi Mungles, having a look now.
Hi Mungles,
Iāve looked into the logs for the correlation ID you provided and can see the A027 (A&G Conversion) request is failing because the service on the referral (Service ID 7965523) is not published.
Iāve confirmed this by checking the database directly. The serviceās published status is currently set to āUNPUBLISHEDā, and the last modified timestamp on that record is 20/04/2026 at 11:54, which lines up with when you started seeing the 422 errors. This suggests the service was unpublished on that date, and any A&G conversion requests referencing it have been failing since then.
Iād need to check the other failing correlation IDs to confirm this is the sole cause of the elevated 422s, but based on what Iāve seen so far, this unpublished service is the reason for the errors youāre experiencing.
As a next step, could you check with the service provider whether this service was intentionally unpublished? If it needs to be re-published, that should resolve the issue.
Hi George, Thank you for looking into this.
Here are a couple more, could you check if they are the same? I will contact the service provider to investigate.
145f99e9-dfc3-4e59-a39e-044b0fbb7ec9
9513c7c8-a5d7-4258-bf1d-96dbc1f908ce
I will check these now.
For correlation ID - 145f99e9-dfc3-4e59-a39e-044b0fbb7ec9, the same applies. The service with ID ā7963620ā is not published (last edited 20/04/2026) and this has been verified in prod DB.
However for correlation ID - 9513c7c8-a5d7-4258-bf1d-96dbc1f908ce, there is a slightly different error message, stating that the A&G request must be in progress. This suggests the A&G has already been actioned or is no longer active. Could you confirm whether this instance returned a null body too?
Ah my bad. In the latter case there was a response body. Thank you for confirming. We have communicated this to our consuming organizations, who have now modified their eRS configuration.
Brilliant let me know how that goes!
Hi all - can I please point out that this developer community should not be used to discuss production/ live issues. In future, please raise these via the National Service Desk:
Ā· Online: https://www.support.digitalservices.nhs.uk/csm
Ā· Telephone: 0300 303 5035
Ā· Email: ssd.nationalservicedesk@nhs.net