Temporal

Advanced Visibility Filtering Capabilities Unavailable Without Proper Database

info
configurationUpdated Mar 3, 2026

Advanced Visibility features including custom SQL-like List Filters for listing, filtering, and sorting Workflow Executions require specific database configurations. Without proper setup, operators cannot leverage enhanced query capabilities.

Technologies:
How to detect:

Need for advanced Visibility capabilities (custom SQL-like List Filters) without appropriate database configuration supporting advanced Visibility features

Recommended action:

1. Determine Temporal Server version to identify supported databases. 2. For version 1.20+: Configure MySQL 8.0.17+, PostgreSQL 12+, or Elasticsearch as Visibility store. 3. For version 1.19.1 and earlier: Integrate with Elasticsearch (only supported option). 4. Configure Visibility store connection in Temporal Service configuration. 5. Test List Filter queries using custom SQL-like syntax. 6. Document available Search Attributes for operators and developers. 7. Train team on advanced query capabilities. 8. On Temporal Cloud: Advanced Visibility is enabled by default, no configuration needed.