A failed read of the plan ladders replaces a member's whole entitlements panel with a plans error #206

New Issue

2026-10-09T16:03:02Z

cgalo5758 commented

2026-10-09 16:03:02 +00:00

What happens

The "Your entitlements" panel on the Products page shows four things for the member's organization: the tier it holds on each plan ladder (a named set of tiers a member moves up and down), its numeric limits with their usage, the capabilities it includes, and where these come from. buildEntitlementsData makes those reads in turn and keeps one error for all of them, EntitlementsData.Error. When that error is set, the template shows it in place of the whole panel.

The plan lines are built last. They need the list of every ladder (ListPlanLadders), but only to name each line and to order the lines the way the plans region does. When that list cannot be read, ladderRows returns the error after the limits, usage, capabilities and sources have all been read. The member then sees one alert, "Error: Failed to load plans", where all of them would be. The plans region below reads the same list and, when that read fails, shows the same words.

The panel's other reads each fail in their own way:

A failed limits or usage read shows its error and nothing else.
A failed capabilities or sources read leaves that part empty, with no error.
A failed read of the tiers held shows "No active plan" (#197).

What should happen

A failed read takes out only the part of the panel it feeds, and that part says it failed. When the ladder list cannot be read, the error stands where the plan lines go, and the limits, capabilities and sources show below it.

The operator's organization page already works this way: one loader per section, each with its own error field (loadOrgGrants and GrantsError in internal/server/operator_enrollment.go). #121 proposes that shape for any page made of several sections. #121 only moves code and changes nothing anyone sees, so it does not cover this.

#197 asks the panel to show its load error when the read of the tiers held fails. With today's single error field, that error would hide the limits as well.

Where

internal/server/member_entitlements.go (buildEntitlementsData, ladderRows) and internal/embeds/templates/partials/member_entitlements.html. TestMemberEntitlementsReadFailures in internal/server/member_entitlements_db_test.go pins today's behaviour.

Why it matters

A brief fault in a read that only names the plan lines hides a member's limits and usage, which were read correctly, and shows a plans error under the entitlements heading.

## What happens The "Your entitlements" panel on the Products page shows four things for the member's organization: the tier it holds on each plan ladder (a named set of tiers a member moves up and down), its numeric limits with their usage, the capabilities it includes, and where these come from. `buildEntitlementsData` makes those reads in turn and keeps one error for all of them, `EntitlementsData.Error`. When that error is set, the template shows it in place of the whole panel. The plan lines are built last. They need the list of every ladder (`ListPlanLadders`), but only to name each line and to order the lines the way the plans region does. When that list cannot be read, `ladderRows` returns the error after the limits, usage, capabilities and sources have all been read. The member then sees one alert, "Error: Failed to load plans", where all of them would be. The plans region below reads the same list and, when that read fails, shows the same words. The panel's other reads each fail in their own way: - A failed limits or usage read shows its error and nothing else. - A failed capabilities or sources read leaves that part empty, with no error. - A failed read of the tiers held shows "No active plan" (#197). ## What should happen A failed read takes out only the part of the panel it feeds, and that part says it failed. When the ladder list cannot be read, the error stands where the plan lines go, and the limits, capabilities and sources show below it. The operator's organization page already works this way: one loader per section, each with its own error field (`loadOrgGrants` and `GrantsError` in `internal/server/operator_enrollment.go`). #121 proposes that shape for any page made of several sections. #121 only moves code and changes nothing anyone sees, so it does not cover this. #197 asks the panel to show its load error when the read of the tiers held fails. With today's single error field, that error would hide the limits as well. ## Where `internal/server/member_entitlements.go` (`buildEntitlementsData`, `ladderRows`) and `internal/embeds/templates/partials/member_entitlements.html`. `TestMemberEntitlementsReadFailures` in `internal/server/member_entitlements_db_test.go` pins today's behaviour. ## Why it matters A brief fault in a read that only names the plan lines hides a member's limits and usage, which were read correctly, and shows a plans error under the entitlements heading.

cgalo5758 added the

kind

bug

area/entitlements area/member-ui labels 2026-10-09 16:03:02 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#206