Query Timeout for User Search Cannot Be Configured

This article clarifies whether the timeout period for user search queries can be adjusted. The user search best practices documentation indicates that search queries time out, returning an HTTP status code 503, if completion is not achieved in two seconds or less.

• User search functionality

• Layer0 environments

• Search queries returning an HTTP status code 503

Search queries are designed to return an HTTP status code 503 if they do not complete within two seconds. Queries that take longer than this duration are either computationally expensive or contain an error preventing quick completion.

The query timeout for user search is not configurable.

The best practice is to avoid running expensive queries, even if they complete within the two-second timeout, as this may negatively affect overall database performance.

If issues with search queries timing out are encountered, reach out to support for potential assistance with query optimization.