Issue Summary

API requests to POST /rest/api/2/workflowscheme/read and POST /rest/api/3/workflowscheme/read for team-managed projects return a 500 Internal Server Error with the following response body:

{
  "message": "Cannot read field \"id\" because \"initialData\" is null",
  "status-code": 500,
  "stack-trace": ""
} 

Steps to Reproduce

1. Send a POST request to /rest/api/3/workflowscheme/read (or /rest/api/2/workflowscheme/read) with the following JSON body:

{
  "projectIds": ["<TeamManagedProjectID>"]
} 

1. Observe the API response.

Expected Results

A valid workflow scheme response should be returned for team-managed projects.

Actual Results

A 500 Internal Server Error is returned:

{
  "message": "Cannot read field \"id\" because \"initialData\" is null",
  "status-code": 500,
  "stack-trace": ""
} 

The below exception is thrown in the logs:
NullPointerException: Cannot read field "id" because "initialData" is null

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Additional Context:

• The issue only affects team-managed projects; company-managed projects work as expected.

• Internal investigation points to a null pointer/data integrity issue in the backend.

• This issue started after the deprecation of the expands parameter in the workflow scheme API (2025-07-07), which may have caused data handling regressions.

• The bug was confirmed by engineering after reviewing logs and source code.