Nested experiments now simply track the nesting
What does this MR do and why?
This exception is causing an issue for nested experiments.
The idea of the exception is that in testing this should be noticed and captured, but it looks like the testing may not have allowed the code path to reach the nested experiment, so we want to make it a bit more forgiving, and instead shifting the capability to the reporting layer. Because of this we track an event, using the same logic that's defined in configuration.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.