Asana breaking change: POST /tasks/{task_gid}/time_tracking_entries
Validated schema comparison changed the request accepted instance set.
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
Operation-level change- Rule ID
schema.request_acceptance_narrowed- Classifier version
2026-10-15.2- Direction
- request
- Finding ID
chg_ed21e577bbb07f81ca67dab4c41d9fe9f36d408024a7cf7ecaf92ade6efcc9b4
What is the recorded before and after evidence?
Previous specification SHA-256: e418c0c7538e75757bc03ec8fd90da5a27afc0e0a2b52b64cdfb5f5e8322f366
Revised specification SHA-256: fa07aa82dd06b7bb95cade3e3d8c444854a9c8d154f47f03fa20785341f32c57
Publisher version: 1.0 to 1.0.
...
guide](/docs/inputoutput-options#selecting-nested-fields).
example:
+ - assignee
+ - assignee.name
- attributable_to
- attributable_to.name
...
items:
enum:
+ - assignee
+ - assignee.name
- attributable_to
- attributable_to.name
...
description: A generic Asana Resource, containing a globally unique identifier.
properties:
+ assignee:
+ allOf:
+ - description: A *user* object represents an account in Asana that can be given
+ access to various workspaces, projects, and tasks.
+ properties:
+ gid:
+ description: Globally unique identifier of the resource, as a string.
+ example: "12345"
+ readOnly: true
+ type: string
+ x-insert-after: false
+ name:
+ description: "*Read-only except when same user as requester*. The user's name."
+ example: Greg Sanchez
+ type: string
+ resource_type:
+ description: The base type of this resource.
+ example: user
+ readOnly: true
+ type: string
+ x-insert-after: gid
+ type: object
+ - description: The user this entry's logged time is attributed to.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