@Marie I think Product might be on the right track
These Approval tasks are part of a very unusual but effective workflow; in fact, they contain 31 Subtasks. When the task gets approved, it triggers a rule that creates a project out of it (just to explain at a high level why there are so many Subtasks).
Thanks @Rosario_Messina! Our team just confirmed this is product limitation.
With “None” sort applied, Asana aggregate the custom field value from the subtasks, but it limit that aggregation to 30 subtasks and won’t display a value if any task has more than 30 subtasks.
We’re always working toward pushing these limits, but until we can do something for this specific limitation I hope you can trim down this set of subtasks to 30.