Help Needed - Test Failure in "Nominal planning: conflict with higher priority" Scenario - utmverse_pre_qual_transition

[utmverse]

Observed behavior
During the "Nominal planning: conflict with higher priority" test scenario, the test run fails with a KeyError exception:

KeyError: 'utmverse_uss'
The error originates from notification_checker.py at line 133.

Based on the test result URLs, the codebase version appears to be commit 101c9be.

I don't have direct access to download the report.json or sequence view artifact from the RPAS Platform test runner, but I can provide the scenario reference from the test results page.
https://results.utmverse.com/us-pre-qual/utmverse_pre_qual_transition/2025-12-28_18%3A38%3A26/sequence/

Test check

1. Scenario: Nominal planning: conflict with higher priority
2. Sequence index: s90 (us-qual-partners) / s178 (us-pre-qual)
3. Error location: notification_checker.py:133 in _maybe_record_note function

Difference from expected behavior
Our USS returns {"user_notifications": []} when queried at /flight_planning/v1/user_notifications because we did not detect a conflict condition that would generate a notification (our flight had higher priority than the existing one). We believe this is compliant behavior.

We're not certain if:

Our USS should be returning something different in this scenario, or
There's an issue with how the test harness handles empty notification responses
Any guidance would be appreciated.

Additional context

Platforms tested: us-qual-partners and us-pre-qual
Our USS endpoint /flight_planning/v1/user_notifications returns a valid JSON response with the schema {"user_notifications": []} when no notifications are present
Other test scenarios involving the same endpoint pass successfully

[BenjaminPelletier]

An exception in uss_qualifier (indicated as red at the bottom of the scenario page of the sequence view and red on the scenario name in the sequence view index) is always a bug, though I believe this one was resolved in September with #1170.

That said, it looks like the bug is being elicited by non-compliant USS behavior. When Flight 2 is planned, Flight 2 conflicts with Flight 1. This conflict is allowed because Flight 2 is of higher priority than Flight 1. However, SCD0090 reads:

When a managing USS creates or modifies an operational intent that conflicts with another operational intent, that USS shall (SCD0090) send a notification reporting the conflict to UAS personnel or the operator’s automation system associated with the new or modified operational intent within ConflictingOIMaxUserNotificationTime seconds, 95 % of the time.

Therefore, the manager of Flight 2 needs to send a notification to the operator ("UAS personnel or the operator's automation system"). This is what uss_qualifier is looking for in the "Check for conflict notifications" step.

Does that resolve the issue?

[utmverse]

Thanks. That helps.