Calling Get Workflow Schemes API sometimes returns undefined instead of an ID

We are using the Get Workflow schemes API by calling the endpoint below inside of our connect app to return all workflow schemes for projects when we return the workflows.

/rest/api/2/workflowscheme/project

However, on certain occasions we are seeing the response from Atlassian is returning an undefined property instead of an ID when a workflow scheme should always have an ID which leads us to see errors similar to below in Sentry.

Decoding failed (Get workflow scheme associations) (1 error) | Expecting number at values.0.workflowScheme.id but instead got: undefined

We have been seeing this issue occur since the start of May according to our logs and this appears to be an issue caused by the Atlassian side and we wanted to know if this a known issue and if so when this will be fixed so that the API never returns undefined as a value for the ID property of a workflow scheme?

Regards,
Kristian

1 Like

Hi @kwalker ,

Thanks for reporting this. I’ve created JRACLOUD-77102 for the Jira Cloud team to address.

Regards,
Dugald

Hi Dugald,

Thank you very much for your response.

We will monitor the ticket with the Jira Cloud team.

Regards,
Kristian

1 Like