# nwSkipTotal = false is limiting out at 100,000 when true result is higher

**URL:** https://community.nextw.com/t/nwskiptotal-false-is-limiting-out-at-100-000-when-true-result-is-higher/928
**Category:** Nextworld Platform
**Created:** [July 31, 2025, 3:06pm UTC](https://community.nextw.com/t/nwskiptotal-false-is-limiting-out-at-100-000-when-true-result-is-higher/928 "2025-07-31T15:06:57Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ian.p](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/ian.p/32/427_2.png) [@ian.p](https://community.nextw.com/u/ian.p)
#### Post date: [July 31, 2025, 3:06pm UTC](https://community.nextw.com/t/nwskiptotal-false-is-limiting-out-at-100-000-when-true-result-is-higher/928/1 "2025-07-31T15:06:57Z")

</div>

I’m making an inbound `:fetch` call to the Nextworld API and passing `"nwSkipTotal": false` in the body of the payload.

In the response, it’s telling me the total number of records is `"total": 100000,` but this is not true, I know from making an aggregate call the result is higher.

Is it possible to get the actual number returned somehow?

When I checked the Endpoint Documentation, this parameter is mentioned but I didn’t see any information about how it behaves:

 ![image](https://us1.discourse-cdn.com/flex001/uploads/nextworld/original/1X/5394dc23d1c34be8da2901101737daf19398c34d.png)

---

<div class="post-metadata">

### Author: ![david.schneider](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/david.schneider/32/142_2.png) [@david.schneider](https://community.nextw.com/u/david.schneider)
#### Post date: [July 31, 2025, 3:28pm UTC](https://community.nextw.com/t/nwskiptotal-false-is-limiting-out-at-100-000-when-true-result-is-higher/928/2 "2025-07-31T15:28:40Z")

</div>

When doing a data fetch with `”nwSkipTotal”: false` the platform will return the record count in the `pageData` section of the response up to a certian value. This is done due to the overhead cost of counting the rows in some very large tables. When the record count returned in `pageData` has been capped the `moreRecords` field in the response will be set to `true`.

The get the full record count, regardless of the cap, use the aggregate endpoint you mentioned above.