{"version":"2.1.283","anchor":"artifact-db-query-results-report-ordered-by","canonical_anchor":"artifact-db-query-results-report-ordered-by","heading":"Ordered artifact database queries now report their ordering and warn when more results may exist","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/artifact-db-query-results-report-ordered-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Ordered artifact database queries now report their ordering and warn when more results may exist\n\nArtifact database queries that use order_by now return ordered_by {field, limit} and warn Claude when a full page means more results may exist\n\n**What**\n\nAn Artifact can hold a small database of documents that Claude can query. Two things change when Claude runs one of these queries with `order_by`, which sorts the results by a chosen field:\n\n- The result now includes `ordered_by: {field, limit}`. This repeats the field the results were sorted by and the limit that was actually applied, including a limit Claude did not set itself.\n\n- Ordered queries return a single page. When that page is full, the tool output warns that more results may exist beyond the ones shown. It tells Claude to raise `query.limit`, or to drop `query.order_by` and page through the results with `query.cursor`.\n\n**Why**\n\nBefore, an ordered query gave no sign that it had stopped at a limit, so Claude could treat a partial list as the complete set. Claude now sees the limit that was used and is told how to fetch the rest.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}