{"version":"2.1.310","anchor":"api-error-telemetry-restructured-and-now-includes-modelcalln","canonical_anchor":"api-error-telemetry-restructured-and-now-includes-modelcalln","heading":"Request records now cover side queries and carry more detail","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/api-error-telemetry-restructured-and-now-includes-modelcalln","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Request records now cover side queries and carry more detail\n\nRecords of model requests now cover side queries and include the model call names, and the effort retry message is reworded\n\n**What**\n\nClaude Code keeps internal records of each request it sends to the model and of each request that fails. Two changes extend them:\n\n- Side queries: a side query is a small extra request Claude Code makes to the model next to the main conversation. `sideQuery` can now record its requests, including the model, the amount used, the cost, how long it took and the effort level, on success and on failure. Its message when it retries because an effort setting is not supported was also reworded.\n\n- More detail on failed requests: the record for a failed request is now built through a shared builder and includes `modelCallNames`. How the error is classified now goes through a helper that takes `accountMemoryKeys`. Before, it used the error class directly or a fallback.\n\n**Why**\n\nThis is record-keeping with no visible effect, apart from the reworded retry message. It means side queries are now tracked like other requests to the model.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}