REST API : no result above a certain number with includeVariables query parameter

cancel
Showing results for 
Search instead for 
Did you mean: 
flehannier
Member II

REST API : no result above a certain number with includeVariables query parameter

Hi,

I got a several problem with the REST API.

I need to have all includes variables for a process with the pagination, so i do this query :

maxItems = 100
skipCount = 600
(status = active  AND includeVariables = true )

Result : 

"pagination": {
"count": 46,
"hasMoreItems": true,
"totalItems": 1460,
"skipCount": 600,
"maxItems": 100
} ,entries": [
{
"entry": {
"processDefinitionId": "gestionDemande:4:367697",
"startUserId": "3xplus",
"startActivityId": "startevent1",
"startedAt": "2021-03-29T07:19:42.694+0000",
"id": "498599",
"completed": false,
"processVariables": [...........]

Now id do  :

maxItems = 100
skipCount = 646
(status = active  AND includeVariables = true )

result :

{
"list": {
"pagination": {
"count": 0,
"hasMoreItems": true,
"totalItems": 1461,
"skipCount": 646,
"maxItems": 100
},
"entries": []
}
}

If i remove includeVariables = true

result :

{
"list": {
"pagination": {
"count": 100,
"hasMoreItems": true,
"totalItems": 1461,
"skipCount": 646,
"maxItems": 100
},
"entries": [
{
"entry": {
"processDefinitionId": "gestionDemande:4:367697",
"startUserId": "3xplus",
"startActivityId": "startevent1",
"startedAt": "2021-03-25T13:16:46.958+0000",
"id": "479007",
"completed": false,
"processDefinitionKey": "gestionDemande"
}
}................................

 

So what wrong i do because there are 1461 processes left  ?

Thanks.

 

 

 

1 Reply
diegomaninetti
Member II

Re: REST API : no result above a certain number with includeVariables query parameter

Hallo.

I have the same issue, on the first page:

{
  "list": {
    "pagination": {
      "count": 0,
      "hasMoreItems": true,
      "totalItems": 54626,
      "skipCount": 0,
      "maxItems": 100
    },
    "context": {
      "consistency": {
        "lastTxId": 18291
      }
    },
    "entries": []
  }
}

The problem was solved executing a full solr reindex.

Is there perhaps a better solution?