Unexpected_error

[mattyryOne]

Ive been getting a bunch of UNEXPECTED_ERROR responses from a listMarketProfitAndLoss request, which have been increasing in number of the past few weeks.
Getting these errors make it appear that i havent been matched, but once i check my P/L through the website, it says that i was actually matched

anyone shed any light on this issue?
below is an actual example of the raw messages from yesterday

{
"jsonrpc": "2.0",
"method": "SportsAPING/v1.0/listMarketProfitAndLoss",
"params": {
"marketIds": ["2.101172491"],
"includeSettledBets": false,
"includeBspBets": false,
"netOfCommission": true
},
"id": 1
}

{
"jsonrpc": "2.0",
"error": {
"code": -32099,
"message": "ANGX-0006",
"data": {
"exceptionname": "APINGException",
"APINGException": {
"errorDetails": "",
"errorCode": "UNEXPECTED_ERROR",
"requestUUID": "prdang019-02231809-000315e176"
}
}
},
"id": 1
}

[Joseph Paterson]

Seeing the same thing here, can't get it to respond correctly at all. Nothing has changed at my end and my code was working a few days ago.

[TSDBDP]

I was having this issue but found a work around by changing "netOfCommission": true to "netOfCommission": false.

[BetfairDeveloperProgram]

Hi All,

This issue has been recreated and is being investigated (INC INC0082863).

I'll update this thread as soon as I have further information.

Thanks

Neil

[BetfairDeveloperProgram]

Hi All,

This issue was fixed as part of a release yesterday evening and the service is now behaving as expected.

However, please let us know if you experience any further problems.

Thanks

Neil

[Stolislav]

Hi guys,

I am trying to call the following, but receive an error:

{
"jsonrpc": "2.0",
"method": "SportsAPING/v1.0/listMarketProfitAndLoss",
"params": {
"marketIds": ["1.117678874"],
"includeSettledBets": false,
"includeBspBets": false,
"netOfCommission": false
},
"id": 1
}

This is the error:

'{"jsonrpc":"2.0","error":{"code":-32099,"message":"ANGX-0003","data":{"exceptionname":"APINGException","AP INGException":{"errorDetails":"","errorCode":"INVA LID_SESSION_INFORMATION","requestUUID":"prdang-288286-03201813-0001f11499"}}},"id":1}'


Calling other functions works perfectly fine, so the problem is not in my session key, as stated in this error.