Null wrapUpCode in /analytics/details/conversations query — bug or limitation?

Can anyone clarify why my detail query returns null for wrapUpCode despite valid data existing in the UI?

Context:
I am extracting conversation details to Snowflake using the Genesys Cloud Analytics API. My Python script uses requests to hit /api/v2/analytics/details/conversations. The request succeeds (200 OK), but the wrapUpCode field in the returned JSON objects is consistently null. I verified the interactions manually in the Genesys Cloud interface; agents are definitely assigning wrap-up codes. I have tried including wrapUpCode explicitly in the view parameter and using the default default view. I also checked the groupings parameter, but that seems irrelevant for detail records. I suspect this might be a known limitation of the detail endpoint or a specific filtering issue.

Question:
Is returning null for wrapUpCode a known limitation of the details endpoint? Or is there a specific parameter I am missing to force the inclusion of this field? Here is a snippet of my request payload:

{
 "dateFrom": "2023-10-01T00:00:00.000Z",
 "dateTo": "2023-10-02T00:00:00.000Z",
 "view": "default",
 "groupings": ["wrapUpCode"]
}

Any insights would be appreciated.