Glad you got it sorted. For anyone reading later, this behavior comes from how Tulip handles Table Queries and Aggregations. Aggregations always return a summarized list based on the query they sit on top of. The docs note that queries and aggregations “filter and summarize your data for use in Apps”:
https://support.tulip.co/docs/table-queries-and-aggregations
The Community guide on dynamic single selects shows the same setup, where a “unique values” aggregation is used to populate dropdown options:
https://community.tulip.co/t/using-values-in-one-single-select-menu-to-dynamically-populate-values-in-a-second-single-select-menu-part-1/7251
So if the query feeding the aggregation has a filter, the Single Select will only show the values returned by that filtered result. Removing the filter (or adjusting it) restores the full set of options.
This is expected behavior and consistent with how Tulip queries and aggregations work.