Skip to main content
Feedback

Handling Errors during Post‑Processing

Handling Errors from ASR Service

  • Any HTTP status code other than 2xx series will be considered as error.

  • If "stopOnError" is false, then API Management will log error response in proxy_error log and will not process error response. For example, the response received from target backend point will be sent to the client.

  • If "stopOnError" is true, then API Management will override response retrieved from target backend point.

  • If "stopOnError" is true and error response is retrieved from Transformation Service, then API Management will set the following HTTP response to the client:

    • HTTP Status Code will be set as HTTP status code received in Transformation endpoint response.

    • HTTP Status Message will be set as HTTP status message received in Transformation endpoint response.

    • Headers received in Transformation endpoint response will be set as HTTP headers for client response.

    • Response payload from Transformation endpoint will be set as HTTP response body.

  • If "stopOnError" is true and error occurred while post processing, then API Management will set the following HTTP response according to scenario mentioned in the Call Transformation Error Messages section:

    {
    "errorTitle": "<Text Present Under Error Title Section like
    ASRServiceURLNotDefined>",
    "errorDetail": "<Text Present Under Error Detail Section like Unable to retrieve ASR
    Service URL>",
    "point" : "PostProcessor"
    }

  • If "stopOnError" is false and error occurred while post processing, then API Management will log the following error in proxy_error.log:

    {
    "errorTitle": "<Text Present Under Error Title Section like ASRServiceURLNotDefined>",
    "errorDetail": "<Text Present Under Error Detail Section like Unable to retrieve ASR
    Service URL>",
    "point" : "PostProcessor"
    }
On this Page