Skip to main content

Missing error detail in Claims QC Feedback

Bug Reports

Claims upload summary view (image attached below) shows records rejected as 4 claims each for measure and claim inputs. While the expected result was to see the errors detailed in the QC feedback, there are none.

Please refer to the details for Upload 545 in testing:

https://cedars-3.cpuc.ca.gov/claims/upload-summary/545/.

Select the module in CEDARS
Select user type
Posted by Roopa Reddy ·
Status: Completed6 comments

Log in to comment and vote

Comments6

  • cedars team

    Team•

    Sep 3, 2025

    Hi @RoopaReddy_PGE

    We’ve tracked down what was happening with Upload 545 in cedars-3.

    The four “errors” you saw in the Claims upload summary view aren’t true errors. They come from the last four records in the Measure and Claim files, which reference Program IDs that aren’t included in the ProgramCost file. Right now, the system is treating those missing references as errors but that isn’t quite right, since ProgramCost records can be uploaded later.

    If you remove those records, the upload goes through cleanly with no errors. We are working on making these errors warnings. I’ll let you know when this is ready to test.

    • Roopa Reddy

      •

      Sep 3, 2025

      @cedars team Makes sense. Thank you.

      • cedars team

        Team•

        Sep 9, 2025

        Hi @RoopaReddy_PGE a fix for this is up on cedars-3 if you wanted to test uploading a file with Measures with no matching ProgramCost.

        This is now the expected messaging:

        • Roopa Reddy

          •

          Sep 11, 2025

          @cedars team I did not receive any warnings, instead all QC passed for my test batch with measure data that has no matching ProgramCost data. Please advise when you get a chance. This is low priority.
          Link to my test batch: https://cedars-3.cpuc.ca.gov/claims/upload-summary/584/

          • cedars team

            Team•

            Sep 30, 2025

            Hi Roopa, just following up on your feedback.

            CEDARS performs the following table check: “Measure.PrgID matches with a ProgramCost.PrgID.” This was changed to a warning with the implementation of: https://cpuccedars.featurebase.app/p/2024-claim-spec-update-separate-program-cost-from-other-data.

            Since that update, if the ProgramCost and Measure primary keys don’t match, a warning validation will appear in the Upload History and Upload Summary UI to flag the discrepancy.

            Looking at the file584_PGE_retest_qc_feedback_bug_2.1.zip

            that you used for testing, I can see that PGE_MS_GRC_Overheads is included in both the Measure and ProgramCost files, so no warning is triggered for that upload.


            To test this behavior on cedars-3, I’d suggest uploading a PrgID that hasn’t been included as part of Claims Q3 testing with either a file that includes Measures only, or ProgramCost only.

            • Roopa Reddy

              •

              Oct 3, 2025

              @cedars team I am comfortable with your test results. Please feel free to mark this case as completed. Thank you.