Aggregate endpoint "Cut member not found"

[palamago]

In an Aggregate query like: /cubes/demre_applications/aggregate.jsonrecords?cuts%5B%5D=Report+Year.Year.Year.2020&cuts%5B%5D=Institution.Institution.Institution.7,86,117,70,10,75,76,74,83,71,78&cuts%5B%5D=Preference+Status.Preference+Status.Preference+Status.24&cuts%5B%5D=Career.Career.Generic+Career.193,81,79,82,267,22,157,158,247,188,78,17&drilldowns%5B%5D=Career.Career.Generic+Career&drilldowns%5B%5D=Institution.Institution.Institution&drilldowns%5B%5D=Report+Year.Year.Year&measures%5B%5D=Last%20Enrolled%20Score&parents=false&sparse=false

Tesseract returns 404 with a message:
"Cut member not found"

It means that some id (not sure which one) set in cut param is not present in the members list in this cube/dimension.

Is this behavior correct?
Ignore the cut if not present is not a better plan?

[frabarz]

I think failing loudly is a better approach than failing silently.
We could have a situation where the failing id is actually in the database but the operations can't find it, which might be an indication of a problem in the ingestion process or with tesseract's code itself.

[hwchen]

Not sure why I didn't add which cut member is not found to the error message.

I'm a fan of failing loudly, at least for the core tesseract api. I think that logic layer is more lenient.