# Archival visibility level

**URL:** <https://community.temporal.io/t/archival-visibility-level/9069>\
**Category:** Community Support\
**Tags:** java-sdk, archival\
**Created:** [August 3, 2023, 6:39am UTC](https://community.temporal.io/t/archival-visibility-level/9069 "2023-08-03T06:39:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Noam](https://avatars.discourse-cdn.com/v4/letter/n/57b2e6/32.png) [@Noam](https://community.temporal.io/u/Noam)\
**Post date:** [August 3, 2023, 6:39am UTC](https://community.temporal.io/t/archival-visibility-level/9069/1 "2023-08-03T06:39:32Z")

</div>

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](https://github.com/temporalio/temporal/blob/master/proto/internal/temporal/server/api/archiver/v1/message.proto#L54-L68) - but when looking at the S3 query converter it seems like they aren’t [supported](https://github.com/temporalio/temporal/blob/master/common/archiver/s3store/query_parser.go) 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 🙂