The admin Reports screen fetches four report sections concurrently. The low-stock section's default threshold is sourced from the same settings store as another guarded read, but unlike that read, the low-stock threshold read isn't itself fault-tolerant.
As a result, a settings-store fault currently fails the whole Reports screen instead of degrading gracefully to just the low-stock label.
This now fires for every deployment: the commerce client construction collapsed to always in-process, which removed an earlier mode gate that had been masking the exposure.
A regression test pinning the desired behavior (degrade only the low-stock label on a settings-store fault, keep the rest of the screen working) is parked as test.todo in the reports-widget sandbox test suite pending a fix.
The admin Reports screen fetches four report sections concurrently. The low-stock section's default threshold is sourced from the same settings store as another guarded read, but unlike that read, the low-stock threshold read isn't itself fault-tolerant.
As a result, a settings-store fault currently fails the whole Reports screen instead of degrading gracefully to just the low-stock label.
This now fires for every deployment: the commerce client construction collapsed to always in-process, which removed an earlier mode gate that had been masking the exposure.
A regression test pinning the desired behavior (degrade only the low-stock label on a settings-store fault, keep the rest of the screen working) is parked as
test.todoin the reports-widget sandbox test suite pending a fix.