Error in response of listClearedOrders

[Tipmanager1]

Does anyone else experiencing errors in calls of the listClearedOrders method? I am getting errors like "Too many pending requests to cleared bet reporting service", even when I make the requests one by one.

[AlgoTrader]

Right now:

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "SportsAPING/v1.0/listClearedOrders",
  "params": {
    "betStatus": "SETTLED"
  }
}

Response:{
  "jsonrpc": "2.0",
  "result": {
    "clearedOrders": [
      {
        "eventTypeId": "1",
        "eventId": "27118631",
        "marketId": "1.112263397",
        "selectionId": 48351,
        "handicap": 0,
        "betId": "...",
        "placedDate": "...",
        "persistenceType": "LAPSE",
        "orderType": "LIMIT",
        "side": "BACK",
        "priceRequested": ...,
        "settledDate": "...",
        "betCount": 1,
        "priceMatched": ...,
        "priceReduced": false,
        "sizeSettled": ...,
        "profit": ...
      },
      ...
    ],
    "moreAvailable": false
  },
  "id": 2
}

removed bet identifiers

[mja]

Yes I also see problems with the responses from listClearedOrders.

It seems that some combinations of filter and group by are not supported, i.e. the groupBy level must be equal to or lower than the filtering requirement.

When I was testing this I found that when the filter failed I received data for all my bets (or nothing at all if the call timed out). If I persisted I would eventually get the TOO_MANY_REQUESTS error suggesting the failed calls were still running on the Betfair server.

I have also found that the first time I call listClearedOrders on any given day I get no response after 30 seconds, but if I make the same call again it works straight away.

It seems the database access behind listClearedOrders is not well optimised.

[Tipmanager1]

Thanks for reply.
Indeed, same here, the first call takes much longer than the following ones.
@BDP, when will this be fixed?