Sep 18, 2026
Estimated Cost Per Run, Hub Reports, and a Way Back to V7 Connector Credentials
Every workflow now carries an estimated cost per run, and the Workflows report sorts on it. Hub reports cover uploads, files and chat activity. A connector moved onto your own OAuth client can be moved back.
What a run costs
An estimated cost per run, per workflow: Each workflow shows what a single run is expected to cost, so the expensive ones are visible without reconstructing them from usage rows.
Sort and order by it: The Workflows report has a Cost per run column and orders on it, which puts the costly workflows at the top rather than somewhere in the list.
Average field cost: Reporting shows average field cost per run and per entity computation, so a cost can be traced to the field driving it.
Hub reports
Uploads, files and chat activity: Hub reports carry upload counts and their time series, current file counts, and chat activity against a hub, so a hub reads as something in use rather than a name in a list.
Searches are counted as searches: Hub searches, including the ones a run fans out, are counted in hub activity rather than going unrecorded.
Cost over time: Organization hub reports carry a cost time series.
Reporting breakdowns
Spend split by member: The Overview, Users, Chats, Models, Workflows and Workflow detail series each break down by the members behind them, with a top-member breakdown on spend and every bucket filled for a named cohort.
Per-member detail in charts and tooltips: A chart and its tooltip carry the same breakdown, so hovering answers the question the chart raises.
Comparisons hold under a filter: A filtered Models comparison reads against the right periods, and the Models breakdown applies its predicates after the merge rather than before.
Reporting over MCP: A shared Reporting tool is available over MCP with delegated authentication, so a report can be asked for in the place you are already working.
Connectors
Back to V7 credentials in one click: A connector moved onto your own OAuth client can be switched back to the V7 template client, and a connection left unconfigured uses the template credentials rather than failing.
A refused sign-in reads as a refusal: An OAuth access denial is told apart from a credential failure, so the fix is clear from the message.
Gong call listing: Call listing is routed through the API integration.
Chat and reliability
Tool search respects what is actually runnable: Tool search checks capability types and index readiness, and resolves runnable Workflow eligibility in bulk before ranking, so the top result is something you can run.
An overloaded provider is reported as one: A provider reporting itself overloaded comes back as a tool error rather than an unexplained failure.
Steadier long conversations: Thinking replay errors are gone, empty user messages are dropped, and a compaction checkpoint can no longer be written without the message it came from.
