Fix 500 during proofing verify step when expected information is not present#6118
Fix 500 during proofing verify step when expected information is not present#6118mitchellhenke merged 2 commits intomainfrom
Conversation
|
I kinda wonder if we should be preventing this before it gets to |
a768936 to
c1fdd39
Compare
There was a problem hiding this comment.
I drafted a comment here but it looks like it was updated / fixed in the meantime. Still, depending if we want a one-liner, could be relevant:
Curious about the || here: Looking at the implementation of mark_step_incomplete, I might assume it returns a truthy value, assuming the corresponding step exists, and never hit the return.
Wonder if we could make an explicit (nil?) return value from mark_step_incomplete, and write this as:
return mark_step_incomplete(:ssn) if pii_from_doc.nil?... with added advantage that it's clearer from the start of the line that this is an early return path.
There was a problem hiding this comment.
Yeah, that's a great idea, will give that a go
This was the other primary option I considered, and could be a better/more comprehensive way to solve, since I discovered it also affects the prior |
c1fdd39 to
3ab9860
Compare
There was a problem hiding this comment.
Maybe want to ensure that the #call result is empty, to protect in case a future maintainer decides the nil return in mark_step_incomplete is redundant?
There was a problem hiding this comment.
Good call, thank you, added
There was a problem hiding this comment.
Should we have one of these specs for ssn_step as well?
There was a problem hiding this comment.
Yep, added new spec file for it
871e7b5 to
4dd9740
Compare
changelog: Bug Fixes, Identity Verification, Fix uncommon errors during proofing at the resolution and SSN steps
4dd9740 to
7f0fb4e
Compare
We had a few errors in New Relic
I suspect there may be other paths to get into this state, but I was able to reproduce with:
It's likely an uncommon path towards a 500, but the result is: