The function runtime compiled using the most recent pull requests and function app version change commit no longer returns a success code of 200 to the service hook in Azure DevOps. It appears that line 83 of AzureFunctionHandler.cs is the issue:
return req.CreateResponse(HttpStatusCode.OK, execResult);
The tooltip states that if no formatter is found then CreateResponse will return 406: Not Acceptable, which is what ends up being returned to the service hook which interprets it as having failed. Changing the line as seen here fixes the issue:
return req.CreateResponse(HttpStatusCode.OK);
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The function runtime compiled using the most recent pull requests and function app version change commit no longer returns a success code of 200 to the service hook in Azure DevOps. It appears that line 83 of AzureFunctionHandler.cs is the issue:
return req.CreateResponse(HttpStatusCode.OK, execResult);
The tooltip states that if no formatter is found then CreateResponse will return 406: Not Acceptable, which is what ends up being returned to the service hook which interprets it as having failed. Changing the line as seen here fixes the issue:
return req.CreateResponse(HttpStatusCode.OK);