;
monitor.subscribe(FindManagedObjectResponse.SUBSCRIBE_CHANNEL);
on all FindManagedObjectResponse(reqId=findManagedObject.reqId) as resp and not FindManagedObjectResponseAck(reqId=findManagedObject.reqId) {
ids.append(resp.managedObject.id);
}
on FindManagedObjectResponseAck(reqId=findManagedObject.reqId) {
monitor.unsubscribe(FindManagedObjectResponse.SUBSCRIBE_CHANNEL);
log "Count: " + ids.size() at INFO;
}
send findManagedObject to FindManagedObject.SEND_CHANNEL;
}
```
---
### Author:  [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)
#### Post date: [December 23, 2025, 8:45am UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/7 "2025-12-23T08:45:15Z")
> [@bdm](#):
>
> findManagedObject.params.add(“query”, “$filter=(has(c8y\_IsDevice))”);
> send findManagedObject to FindManagedObject.SEND\_CHANNEL;
Two observations:
- use “fragment” instead of “query” will be faster
- you should only do the “send” after you have established the listener like you can see in my example as you otherwise might get responses before you have a listener reacting to them.
---
### Author:  [@bdm](https://community.cumulocity.com/u/bdm)
#### Post date: [December 23, 2025, 9:05am UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/8 "2025-12-23T09:05:28Z")
ok thanks, I will test that. So conclusion : in EPL to get more than 3000+ managed objects there is no need for pageSize and Pagination (currentPage) params in order to get the full response, Pagination happens automatically?
unlike API calls for example from postman or python (where maximum page size is 2000 managed objects) correct?
Initially we thought that the 2000 managed objects limit applies to EPL just like how it applies to inventory API, but the initial search (which might have been missleading) indicated that API calls to Inventory REST API directly have a limit of 2000 managed object per page, while Apama is going through the Cumulocity Java SDK / Microservice layer which enforces a 1000-item cap.
---
### Author:  [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)
#### Post date: [December 23, 2025, 9:19am UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/9 "2025-12-23T09:19:47Z")
Correct, no need to do anything with pageSize or currentPage (in most cases).
EPL like the JavaSDK are still bound to the 2000 item page size limit of Cumulocity but they provide abstractions on top of it that mean you do not have to care about it yourself.
The 1000 item limit use by EPL is compromise to efficiently load many items once but not going to the 2000 item page limit of the API, which could actually be less efficient when processing in EPL.
---
### Author:  [@bdm](https://community.cumulocity.com/u/bdm)
#### Post date: [December 23, 2025, 9:48am UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/10 "2025-12-23T09:48:39Z")
> [@Harald\_Meyer](#):
>
> `fragmentType`
ok, could “query“ param be the tricky reason for automatic pagination issue? and maybe simply replacing it by “fragmentType“ solves pagination?
---
### Author:  [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)
#### Post date: [December 23, 2025, 10:21am UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/11 "2025-12-23T10:21:21Z")
I tested with both and both worked for me correctly.
---
### Author:  [@bdm](https://community.cumulocity.com/u/bdm)
#### Post date: [January 5, 2026, 2:58pm UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/12 "2026-01-05T14:58:14Z")
ok thanks, from your perspective, what was the reason why my initial code before pagination didn’t get all the managed objects?
could it be because pagesize was defined?
my code: pagesize defined to 2000, while it seems EPL supports only 1000 in one page
your code: no explicit page size, could it be the reason? and what would be the pagesize here? default 5 like postman? while pagination happens automatically
---
### Author:  [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)
#### Post date: [January 5, 2026, 3:34pm UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/13 "2026-01-05T15:34:36Z")
It should have worked with pageSize=2000. I did a test and I received all 2000 matching objects. Are you sure
- you did not also provide a “currentPage” as well?
- other filter parameters that may have reduced the number of matching objects?
- or established the listener after you did the “send” of the FindManagedObject request?
If you do not provide a pageSize, a page size of 1000 is used, which is a good compromise for most use cases.
---
### Author:  [@bdm](https://community.cumulocity.com/u/bdm)
#### Post date: [January 7, 2026, 5:08pm UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/14 "2026-01-07T17:08:32Z")
in our case now the expected Managed objects are greater than 2000, we are receiving now 3125 managed objects and this number will increase daily, does it change anything in the previous feedback? or you already tested a number greater than 2000 ?
---
### Author:  [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)
#### Post date: [January 8, 2026, 6:39am UTC](https://community.cumulocity.com/t/epl-interaction-with-cumulocity-api-maximum-page-size/14150/15 "2026-01-08T06:39:06Z")
I tested with around 2100 managed objects not providing a page size, so the default of 1000 was used. I received all expected managed objects in my EPL App.