Troubleshooting Rally API Calls failing intermittently even though a 200 http status was received
search cancel

Troubleshooting Rally API Calls failing intermittently even though a 200 http status was received

book

Article ID: 389543

calendar_today

Updated On:

Products

Rally SaaS

Issue/Introduction

The API response shows 200 status, no errors, and “Disabled” set to true for the user. But when going into the UI, the user is still enabled.

This has worked to disable many users, but there are several that this isn’t working for.

Resolution

When a 200 HTTP status is received, it just means that Rally has processed the call.  Rally may have sent an error in the response to the API call that was made.  If there is an error reading the object, it will return a status of 200 and an <OperationResult>  document is returned with a list of errors. The 200 (HTTP success) code will not return an HTTP error code. The update and delete operations also return this document. Warnings can be ignored, but errors indicate that the requested operation has failed.  Here is an example of what the error looks like:

{ operationresult:{ _rallyAPIMajor: "2", _rallyAPIMinor: "0", errors:{ operationresulterror:'Some error text here' }, warnings:{ operationresultwarning:'Some warning text here' } } }
 
In my "errored" response I see the following:
 
{
{
"_rallyAPIMajor": "2",
"_rallyAPIMinor": "0",
[
"Could not convert: \"ScheduleState\" must be a string : Value [ Dummy ] for field [ string ] is invalid. Valid values are: [ Active, Defined, In-Progress, Completed, Accepted, Closed ]"
],
[
]
 
Please check your responses to the specific calls in question to see if we sent an error.