Got a massive problem... too many records to handle being returned, 28000 and counting, so decided to revisit the API filter options which says:

Optional parameters are (can be combined):

    Limit: Defines the number of results returned. Default is 25.
    Offset: Defines how many results are skipped before the API returns any data. Default is 0.
    SortBy: Defines the sorting order of the results. Options are: DeviceId, SentTime, ReportDeadline, ReceivedTime or CpuTime. Default is SentTime.
    Format: The format of the data. Options are XML or JSON. Default is JSON.
    ModTime: Return results which were last modified on or after this time. This value is a Unixtimestamp (number of seconds since midnight Jan 1 1970).
    ServerState: Return results based on whether they are currently in progress or have already been reported back to World Community Grid. 4 would return in-progress results, 5 would return results which have already been reported back to the server.
    Outcome: Return results based on the outcome of their processing. 1 means success, 3 means error, 4 means no reply, 6 means validation error, 7 means abandoned./
    ValidateState: Return results based on the validation status. 0 means pending validation, 1 means valid, 2 means invalid, 4 means pending verification, 5 means results failed to validate within given deadline.

What I wanted to achieve was primary sort on Received Time, then secondary filter on the Modtime, on or after, with the latter part of the URL formatted as follows, the Modtime seconds per unix at start of this statistics period which is 1481500800 aka 161212 at 00:00:00

&format=xml&limit=250&offset=0&ServerState=5&SortBy=ReceivedTime&=ModTime=1481500800

What is being returned as top record with application of an offset of 250 is a result with a modtime from before the last modified on or after this time ... the query response does not want to be convinced to adhere to my requirements

<?xml version="1.0" encoding="UTF-8" ?>
- <ResultsStatus>
<ResultsAvailable>860</ResultsAvailable>
<ResultsReturned>250</ResultsReturned>
<Offset>250</Offset>
- <Result>
<AppName>fahv</AppName>
<ClaimedCredit>17.04168537594135</ClaimedCredit>
<CpuTime>1.1776388883590698</CpuTime>
<ElapsedTime>1.1856697797775269</ElapsedTime>
<ExitStatus>0</ExitStatus>
<GrantedCredit>17.04168537594135</GrantedCredit>
<DeviceId>3483292</DeviceId>
<DeviceName>uhuh</DeviceName>
<ModTime>1481498153</ModTime>
<Name>FAHV_1000137_4xfx_P1_Rigid_4525_0</Name>
<Outcome>1</Outcome>
<ReceivedTime>2016-12-11T23:15:48</ReceivedTime>
<ReportDeadline>2016-12-21T10:30:35</ReportDeadline>
<SentTime>2016-12-11T10:30:35</SentTime>
<ServerState>5</ServerState>
<ValidateState>1</ValidateState>
<FileDeleteState>2</FileDeleteState>
</Result>

Is this a bug, or is it me, the construction of the URL query (I hope so, as that's quickly adjustable).

Many thanks in advance (fellow API utilizers too if they know the answer)

edit: Questionmark in title of course