Skip to main content
This is 2026.9 documentation. Coverage here is incremental: a page exists only where 2026.9 differs or is newly documented. For any other topic, switch to Current (2026.8 and earlier) in the version selector.
Automate still runs your functions against models in the 2026.9 data model, exactly as described in Who’s affected. A run against a 2026.9-format model completes, and its results are recorded, the same as any other run.
This page is about seeing results in the product UI. If your function calls AttachResultToObjects or attach_result_to_objects inside the run itself, see Attaching results in 2026.9 for that separate caveat.
The results indicator in the product UI and a documented API don’t cover a model in the 2026.9 format right now. The Dashboards Automate results widget is the way to see them. If you’re troubleshooting a run that appears to have succeeded but produced nothing visible in the viewer, this is why — it isn’t a sign the run failed.

​
What’s missing

For a model still in the current (pre-2026.9) data model, results show up exactly as described in Viewing Automation Results: a doughnut icon in the 3D viewer and in the project model list, both opening the same results summary. For a model in the 2026.9 data model, that icon does not appear in either place. This isn’t specific to any one function or trigger — it applies to any 2026.9-format model with a completed run. There’s also no documented, supported API to read the results back as a substitute. Automate functions can write results during a run, but nothing on this site currently documents a query for reading them back afterwards. (The equivalent gap for Data Validation checks specifically is tracked separately; an undocumented internal path exists there but carries no stability guarantee — see Data Validation if that’s what you’re looking for.)

​
Results in dashboards

Dashboards include an Automate results widget that shows a version’s automation runs and the results each function recorded, and isolates the objects a result refers to in the dashboard’s 3D view. It reads a result’s object ids and matches them to objects in the model by applicationId, so it works for the same reason new runs do and not for results stored against a content-hashed id before the model was migrated.

​
What to do meanwhile

1

Add the Automate results widget to a dashboard

Add the widget to a dashboard on the project and pick the model and version. It lists the runs and their results, and selecting a result isolates its objects in the 3D view.
2

Keep the workspace on compatibility mode

If you need to see results for a model that would otherwise land in the 2026.9 format — through ACC sync or drag-and-drop upload — ask us to switch the workspace into compatibility mode. It keeps that data in the format the current viewer and dashboard already render correctly. See Data model migration for workspaces.
Compatibility mode is a bridge, not a fix. It ends for every workspace on 1 November 2026.
3

Confirm the run actually completed

Check the automation’s run history from project Settings → Automations rather than looking for the results icon. A completed run with no visible icon is this limitation, not a failure.

​
FAQ

Yes, if the run history shows it completed. The results icon and any API read path are what’s missing for 2026.9-format models — the run itself, and what it produced, aren’t affected.
Yes, through the Dashboards Automate results widget. The other option is compatibility mode, which keeps new data in the format the existing viewer supports, so the results icon stays visible the normal way until compatibility mode ends on 1 November 2026.
No committed date yet. It depends on the same underlying frontend work covering the 2026.9 data model more broadly — see Viewer developer notes in 2026.9 for the closest thing to a timeline.
Last modified on September 29, 2026