API CHANGE TRACKER / Asana

Asana breaking change: GET /workspaces/{workspace_gid}/ai_studio/runs

the response property `data/items/allOf[subschema #2]/rule` became nullable for the status `200`

Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.

Which field and classification rule changed?

Changed field
data/items/allOf[subschema #2]/rule
Rule ID
response.now_optional_or_nullable
Classifier version
2026-10-15.2
Direction
response
Finding ID
chg_a608c037e7f5eb445b9c80b93ad4816ee7f6b769386388f3706cc455274fb3a5

What is the recorded before and after evidence?

Previous specification SHA-256: 2cc9d7bc1b36bb225e5f23dfbe571e61bb6e4a33a06d679820c8bf042d5df313

Revised specification SHA-256: 33ddc08cb8abd5e9dd6c2c290b9220983773fda7d3c32d200c98e2df864bcd86

Publisher version: 1.0 to 1.0.

  ...
                          serves as the de-duplication key for incremental loads.
                        properties:
+                         automation:
+                           description: The multi-step automation (AutomationWorkflow) the step belonged to
+                             when it ran. `null` for standalone rules. Non-null
+                             for workflow steps regardless of whether the step
+                             itself was later deleted. Each step of a multi-step
+                             automation run is returned as its own row with the
+                             same `automation`, so group by `automation.gid` to
+                             reconstruct per-automation usage. Not
+                             dereferenceable yet (no public Automations API).
+                           nullable: true
+                           properties:
+                             gid:
+                               example: "1208222222222222"
+                               readOnly: true
+                               type: string
+                             name:
+                               example: Intake triage automation
+                               readOnly: true
+                               type: string
+                             resource_type:
+                               example: automation
+                               readOnly: true
+                               type: string
+                           readOnly: true
+                           type: object
                          credit_source:
                            description: Whether the credits were drawn from a paid or free balance.
  ...
                            type: string
                          rule:
-                           description: The rule (automation) that ran, as a compact reference. The Rules
-                             API is not yet public, so this is not
+                           description: The rule (AutomationStep) that ran, as a compact reference.
+                             Non-null for both standalone rules and multi-step
+                             automation steps as long as the step still exists.
+                             `null` if the step was deleted after the run. The
+                             Rules API is not yet public, so this is not

Inspect the complete release · Public source findings · Publisher specification source

How do I check whether this affects my code?

Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.

Check an authorized repository · Review coverage · Inspect classification rules