NR UI: should not call PATCH after failed GET

[severinbeauvais]

Describe the bug in current situation
According to this Sentry issue, the NR UI does a PATCH call (to update a NR) after a GET call failed.

The failed GET call should stop whatever processing is going on.

Calling PATCH with invalid data (due to failed GET) could save corrupt data in the db and/or overwrite valid data. These errors happened on the checkout call, so cannot corrupt data. However, I am not sure what the app does after this error occurs: Does it force the user to restart from the beginning? Or does it happily continue as if nothing happened, and possibly allow a subsequent checkin... I don't know; the priority should depend on this.

Link bug to the User Story

Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.

Chance of Occurring (high/medium/low/very low)

Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?

Steps to Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Actual/ observed behavior/ results

Expected behavior
A clear and concise description of what you expected to happen. Use the gherking language.

Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

[jdyck-fw]

This is a timebox to review code and verify if this is an issue, and then fix it if it is.

[ozamani9gh]

Old Sentry issue. closing because need recent error message to investigate