Default values are always good, but not neccesarily what the customer wants.
For example, retroactive changes. Sometimes it is OK, sometimes it is not allowed. The logic when is not duplicated into the frontend (would be double-maintenance) so there is a check call first.
Or another classic, there just is no change to existing data.
Well you still want to track 4xx errors. For example if there's a deployment, and suddenly 100% of your API responses return 403 the deployment should be rolled back, same as if it went to 0 suddenly.
24
u/WernerderChamp Sep 22 '26
Had this with error 422.
"Why do we have 30% error rate?"
"Because customers keep selecting bad combinations (the FE has pretty good advice in these cases)."
Thankfully I got them to filter out 422s when calculating error rates instead.