How to debug failing calls properly?

[RalfBarth]

Hello all,

i'm having a hard time to properly debug failing calls to the Azure DevOps APIs, e.g. when creating work items through this MCP server. Is there any facility that shows the raw HTTP request and response?

The only response i see is from the call itself: "The work item was not created" - which is not helpful at all.

Thank you!

[danhellem]

If you are able to make other calls successfully, then the issue is like some kind of rules on the WIT that is preventing the work item from being created. We should be returning an error response though is something does fail. If you are seeing something different, please dig into the root and then let us know and we can repro and put in some better error handling.

[RalfBarth]

Thank you, Dan.

I was able to find the root cause of the failing call: It was due to an invalid value for the AreaPath field of the work item. That fields only accepts a fixed list of values for which i provided an unknown one.

I suppose the API responds with a proper error description and status code, so least i would expect is to simply log such http error messages to the console.