fix(app, react-api-client): handle failed analysis for RTP protocol on ODD #15101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RQA-2673
Overview
RTP protocols introduce a new scenario where an RTP protocol can be sent to a Flex, analyze successfully with default values, and then have parameters input that will cause a failed analysis.
To handle this, the ProtocolSetup on the ODD should promp the user with a failed analysis modal with call to action return to protocol setup to reselect parameters and start a new run. Keeping consistent with our current behavior for protocols that fail analysis, the user will still have the option to dismiss the re-parameterization CTA and proceed with the run.
In addition, we need to modify the ProtocolCard on ODD to search not only for the most recent analysis, but the most recent successful analysis, should one exist.
TODO
Screen.Recording.2024-05-06.at.2.12.55.PM.mov
Test Plan
A. Following analysis failed modal CTA
make -C app-shell-odd push-ot3 host={IP}
B. Ignoring analysis failed modal CTA
C. Protocol card finds successful analysis if one exists
Changelog
Review requests
auth js
Risk assessment
medium