Properly log & alert on null response with a Unique Number
lomky opened this issue · comments
Description
We have found a response that follows the null
response formulation, but does have a Unique Number in the response.
Right now this 500
s with an error on attempting to parse the benefit year. Far better to catch this earlier in the process & log a null case.
Not sure whether 'null' should be a Sev-3 or Sev-4.
Acceptance Criteria
-
null
responses (with and without Unique Number) create a distinct log & alert