Currently, only the filter and collation are stored. So for a find and aggregate query whose filter refers to variables defined in "let" or "runtimeConstants" (e.g. here), the analyzeShardKey command wouldn't be able to evaluate the filter and do the synthetic routing. This would cause the command to fail with a PlanExecutor error just as shown in BF-28087.