Story with resource subtype 'enum_custom_field_changed' is lacking the 'custom_field' property

English Forum Developers & API
,
1

Hello,

I’ve recently started receiving stories from the Asana API where the subtype is enum_custom_field_changed but the story doesn’t contain the custom_field object. See example below.

{
  gid: "1215325724227723",
  created_at: "2026-06-02T10:42:22.473Z",
  custom_field: null,
  new_enum_value: {
    gid: "1215295857270865",
    color: "green",
    enabled: true,
    name: "[REDACTED]",
    resource_type: "enum_option",
  },
  old_enum_value: null,
  text: "[REDACTED]",
  type: "system",
  resource_subtype: "enum_custom_field_changed",
  target: {
    gid: "1215325776905716",
    resource_type: "task",
  },
}

This is rare but nevertheless it causes problems processing the API responses. Is this a bug in the API or some edge case that should be handled by the caller?

Best, Tuomas

2

Hi @Tuomas1 and welcome to the Asana Forum!

I checked this on our side, and it looks like the custom field in question has been removed. When a custom field is deleted, the API will no longer return the parent object. Also, querying it via the Custom Fields API will correctly return a 404 Not Found response.

Given that you mentioned this happens only rarely, it’s unlikely to be a bug. It’s most likely occurring in cases where the custom field has been deleted.

I hope this helps clarify the behavior. Let me know if you have any follow-up questions.