Query documentation updated for JSON extraction

isshaddad

·Feb 25, 2026·#3132docs: Query page output dot notation and metadata availability

Documentation for the Query page is being clarified to guide users on extracting JSON fields using dot notation, while confirming that task metadata is not queryable.

The custom query documentation is being refined to help users write more accurate data extractions. Developers building queries against run data will find clearer guidance on exactly what fields are available and how to access them, avoiding common pitfalls with missing data or incorrect extraction methods.

Specifically, the guide now explicitly notes that custom run metadata—the key-value pairs set within tasks—is not accessible from the Query page. To query JSON-based columns like outputs, errors, and metric attributes, users are now instructed to use direct rather than string extraction functions.

The accompanying reflect this change, demonstrating how to filter and select deeply nested properties natively. A typical query using the updated pattern looks like this:

sql

1SELECT output.externalId AS external_id
2FROM runs
3WHERE task_identifier = 'my-task'
4  AND output.externalId = 'something'
5ORDER BY triggered_at DESC

View Original GitHub Description

Clarifies in the Query docs that run metadata is not available on the Query page and that the output column is JSON, so dot notation (e.g. output.externalId) should be used for selecting and filtering. Adds an example that filters by an output field in WHERE