Exact workspace stats past 100,000 records

GET /api/v2/workspaces/{workspace_id}/stats now computes every stat over the whole matching set, however large. It used to stop at 100,000 records: count could only say "more than 100,000", count_by broke down just part of the set, and sum and created_at_range were refused outright. Now a year's revenue total or a breakdown of a big contact list comes back exact whenever it finishes in time, and a stat that cannot is named in unavailable with a reason instead of being skipped up front.

When none of the requested stats can be computed in time, the response is now a 422 telling you to narrow the query, instead of a 503 asking you to try again. Retrying the same query never helped, and an agent following the old advice could loop on it until it gave up.

Agent examples: report a large workspace's real contact total instead of "more than 100,000" · total a year of revenue on a busy store in one call · narrow a stats query that is too large instead of retrying it

Resources: Workspace Stats. Building with an AI agent? Point it at the Stats skill.