{{ message }}
Repository navigation
fix(frontend/recs): return null from effectiveSavingsPct on AWS reconstruction fallback (followup to #321) #323
Description
Once #321's migration ships and the next collector tick repopulates on_demand_cost for AWS rows, evaluate whether to make effectiveSavingsPct return null when the reconstruction fallback would fire on AWS rows — so the UI renders '—' rather than a silently-wrong percentage. Wait until production data confirms the migration succeeded before deciding.
Closes the optional follow-up flagged in #321's fix plan (item 4 in the fix plan).
Activity
cristim commentedon May 28, 2026
Verification: cannot-verify-autopilot. The input bucket linked PR #324, but that PR closes #321 (the on_demand_cost cache flush migration). Issue #323 is a deliberate follow-up: 'wait until production data confirms the migration succeeded before deciding' whether to return null from effectiveSavingsPct on AWS reconstruction fallback. The decision has not been made and no commit closes this issue on origin/feat/multicloud-web-frontend. The effectiveSavingsPct null-return fix exists on branch origin/fix/issue-252-monthly-cost-effective-pct but is not yet merged. Leaving open.
fix(frontend/recs): effectiveSavingsPct returns null for AWS rows wit…
fix(recs): stop double-amortizing upfront in effectiveSavingsPct (AWS…
feat(recs): plumb provider SavingsPercentage to GUI for CLI/GUI parity
feat(recs): plumb provider SavingsPercentage to GUI for CLI/GUI parity
feat(recs): plumb provider SavingsPercentage to GUI for CLI/GUI parity (