Troubleshooting
After sending an RSA Case Management API request to POST /cases or POST /async-requests/case-creation following responses might be returned including technical errors in case of incorrect data provided or some other issues:
Success response status codes
-
Synchronous mode
| # | HTTP Code | response Description | comment |
|---|---|---|---|
| 1 | 201 | Assistance case is fully created. | Roadside assistance case details returned in the response. |
| 2 | 202 | Assistance case is partially created. |
Please notify the involved person to contact the insurance agent. Roadside assistance case details returned in the response. |
-
Asynchronous mode
| # | HTTP Code | response Description | comment |
|---|---|---|---|
| 1 | 202 | The request for further creating the assistance case is accepted. |
Request identifier for roadside assistance case creation returned in the response. Please check the request status not earlier than 15 mins after the request creation using GET /async-requests/{requestId}. |
Request processing statuses
| # | Status code | Substatus code | Substatus description | comment | ERROR solution |
|---|---|---|---|---|---|
| 1 | ACCEPTED |
N/A |
N/A |
Assistance case creation request is successfully accepted for further processing. |
N/A |
| 2 | INPROGRESS | RCC08 | "Beneficiary validation in progress" | Beneficiary is being validated by vehicle data. | N/A |
| 3 | INPROGRESS |
RCC10 |
"Assistance case creation in progress" |
Assistance case is being created. |
N/A |
| 4 | INPROGRESS | RCC11 | "Assistance case created, scheduled task creation in progress" |
Assistance case is created, and insurance agent is still not informed about the case. Case number and ID are available to retrieve. |
N/A |
| 5 | SUCCESS | RCC20 | "Assistance case and scheduled task created" | Assistance case is created, insurance agent is informed about the case. The involved person should wait for the agent call. | N/A |
| 6 | FAILED | RCC09 | "Beneficiary could not be validated" | Beneficiary could not be validated due to technical issues. | Please try to create a new request later. |
| 7 | FAILED | RCC21 | "Assistance case not created" | Assistance case could not be created due to technical issues. | Please try to create a new request later. |
| 8 | FAILED |
RCC22 |
"Assistance case not created, scheduled task not created" |
Assistance case is created, but insurance agent cannot be informed about the case. Case number and ID is available to retrieve. |
Please notify the involved person to contact the insurance agent. |
| 9 | FAILED | RCC26/RCC27 | "Request cannot be processed" | Assistance case creation failed due to technical issues. | Please try to create a new request later. |
| 10 | FAILED | RCC028 | "Request could not be validated" | Assistance case creation request could not be validated due to technical issues. | Please try to create a new request later. |
| 11 | FAILED |
RCC29 |
"Assistance case creation failed due to business validation error" |
Assistance case creation failed since some business errors occurred, such as: invalid license plate number or contract number provided, etc. |
Please see the `result.errors` property data of the API response for more information. |
Selected errors response status codes
| # | HTTP Code | Error CODE | Error Description | condition | Error solution |
|---|---|---|---|---|---|
| 1 | 401 | CE009 | "Unauthorized. Please send your request via the authorized gateway" | NO authorization token (JWT issued by Apigee) provided in the API request | Provide the access token according to Get Started instructions. |
| 2 | 401 | oauth.v2.InvalidAccessToken | "Invalid access token" | Oauth2 Access token missing | Provide the access token according to Get Started instructions. |
| 3 | 401 | keymanagement.service.invalid_access_token | "Invalid access token" | Oauth2 Access token invalid or expired | Provide the access token according to Get Started instructions. |
| 4 | 401 | keymanagement.service.InvalidAPICall AsNoApiProductMatchFound |
"Invalid API call as no API product match found." | API Product not authorized for the dev app | Provide the access token according to Get Started instructions. |
| 5 | 404 | NA | "Not found" | Incorrect request sent by the client (resource path) | Check the request URL correctness so it meets the API specification. |
| 6 | 404 | messaging.adaptors.http.flow.ApplicationNotFound | "Unable to identify proxy for host default and url XXX". | Incorrect request sent by the client (host or base path) | Check the request host or base path correctness so it meets the API specification. |
| 7 | 429 | policies.ratelimit.QuotaViolation | "Rate limit quota violation. Quota limit exceeded. Identifier: XXX." | The quota limit was exceeded | Contact the support team to extend the calls limit. |
| 8 | 502 | messaging.adaptors.http.UnexpectedEOFAtTarget | "Unexpected EOF at target." | Connection to backend failed | Please try again later. |
| 9 | 502 | protocol.http.TooBigLine | "Response line size exceeding 2,048." | Backend unavailable | Please try again later. |
| 10 | 503 | messaging.adaptors.http.flow.NoActiveTargets | "The Service is temporarily unavailable." | Connection to backend cannot be established | Please try again later. |
| 11 | 503 | messaging.adaptors.http.flow.CircuitBreakerOpen | "CircuitBreaker for BCK_XXX GET_info is OPEN and does not permit further calls." | Circuit breaker open for target backend | Please try again later. |
| 12 | 503 | NA | "Service temporary unavailable" | Service temporarily unavailable | Please try again later. |
| 13 | 504 | messaging.adaptors.http.flow.NoActiveTargets | "Gateway Timeout." | Backend timeout | Please try again later. |
