Azure DevOps GetResponseWorkItemSchema failed

(0) Share

Report

Posted on by schuess3

353

Objective:

I would like to create work items in ADO using the "Create Work Item" action.

Permissions:

I can view the project and create items
I am a member of the default project team

Question:

What do i need in place to get around this error?

Error:

The dynamic operation request to API 'visualstudioteamservices' operation 'GetResponseWorkItemSchema' failed with status code 'InternalServerError'. Error response: { "error": { "code": 500, "source": "unitedstates-002.azure-apim.net", "clientRequestId": "ac07a671-05a5-4b71-9fc2-c23a4f9ae365", "message": "BadGateway", "innerError": { "status": 500, "message": "Unknown error occurred\r\nclientRequestId: ac07a671-05a5-4b71-9fc2-c23a4f9ae365", "error": { "message": "Unknown error occurred" }, "source": "vsts-eus2.azconn-eus2-01.p.azurewebsites.net" } } }

Image

**UPDATE**

After Testing more today, it appears that I only face this issue with a certain type of "Work Item Type" called Finance Requirement. This is obviously a custom work item type, not OOTB. Any ideas what could be the cause?

***UPDATE***

Categories:

Using connectors

I have the same question (0)

All responses (6)

Answers (0)

mohsinkhalid 160 on at

Like (0)

Report

Have you tried reconfiguring the connection?

Was this reply helpful? Yes No
schuess3 353 on at

Like (0)

Report

I just made the connection today for the first time but I can rebuild it.

Was this reply helpful? Yes No
schuess3 353 on at

Like (0)

Report

After Testing more today, it appears that I only face this issue with a certain type of "Work Item Type" called Finance Requirement. This is obviously a custom work item type, not OOTB.

It appears to me that the connection is having trouble retrieving the schema of the work item.

"The dynamic operation request to API 'visualstudioteamservices' operation 'GetResponseWorkItemSchema' failed "

Any ideas what could be the cause?

Was this reply helpful? Yes No
A.G Microsoft Employee on at

Like (0)

Report

Hi,

Any fix to this issue ?

Was this reply helpful? Yes No
A.G Microsoft Employee on at

Like (0)

Report

The problem was solved by allowing 3rd Party OAuth Apps on azure devops

Was this reply helpful? Yes No
viietwalkerr 4 on at

Like (1)

Report

I had run into this issue, I also had the "Enable 3rd Party OAuth" setting enabled already

Turns out the issue was that one of the field Names on a custom work item I had, had a special character (# in my case) in the field name (not label name)
Removing this field solve my issue and allowed me to save the flow, hope this helps someone else

Was this reply helpful? Yes No