Archival visibility level

Hey team,

I’m using temporal’s default archival in S3 (via the Java SDK) and want to perform my search based on custom search attributes which are configured; these seem to be supported in the proto - but when looking at the S3 query converter it seems like they aren’t supported and I’m getting indeed the unknown filter name error when listing in my query search attributes alongside WorkflowTypeName . According to the s3 archival readme search attributes don’t appear in the supported column but I was wondering if there is any future endeavor to support it? currently for testing I’m using tctl on my temporal container for example - tctl workflow listarchived -q "WorkflowTypeName='some name' and MY_CUSTOM_SEARCH_ATTRIBUTE='some value'" and getting the above error.
Any help would be much appreciated :slight_smile: