## The problem
Issue databricks/databricks-sdk-py#99 (closed, 10 comments): Although it's not documented, the query history list [endpoint](https://docs.databricks.com/api-explorer/workspace/queryhistory/list) seems to handle `filter_by` properly only if it is passed in the request body rather than as a query param: Ran using databricks-sdk v0.1.5, requests v2.28.2: ``` In [2]: from databricks.sdk import WorkspaceClient In [3]: client = WorkspaceClient(host=..., token [your value] In [4]: from databricks.sdk.service.sql import QueryFilter In [6]: filter_by = QueryFilter.from_dict( ...: { ...: "query_start_time_range": { ...: "start_time_ms": 0, ...: "end_time_ms": int(time.ti

## What fixed it
Query History list() not passing filter_by correctly: the backend-side fix was released, so upgrade the SDK. Note max_results applies per page, not to the total: with a filter matching 10 queries and max_results=1 you make 10 requests. (The maintainers planned to remove max_results and make list() a plain generator.)