Delegation Is an Architecture Constraint, Not a Warning to Ignore
Non-delegable formulas can silently produce incomplete results, making data-source choice and query design correctness issues.
A delegation warning is not merely a performance hint. It can mean the app evaluates only a limited local subset and returns a plausible, incomplete result without telling the user what is missing.
Design queries around operations the data source can execute. Test beyond development-sized datasets. Use indexed fields, delegable predicates and server-side views. If the required query cannot be expressed reliably, change the data architecture rather than increasing the row limit and hoping.
Teach reviewers to treat delegation warnings according to consequence. Missing a record in a convenience list differs from omitting a compliance case.
Correctness at scale depends on knowing where the query executes. If the answer is “partly on the client against the first 2,000 rows”, the warning is an architecture decision waiting to be made.