Scroll far enough through a large result set and paging stops:
Result window ends at 10,000 rows. Narrow your filters (industry, country, title) to reach the rest - or export the full segment.
This is a deliberate cap, not a bug and not a coverage limit. Your count can say 400,000 and every one of those contacts is reachable. What is capped is walking a result set page by page, because that is how a database gets copied record by record.
The two ways to reach the rest
- Narrow the filters. Split the segment along an axis you care about anyway: one country at a time, one industry at a time, one seniority band at a time. Each slice pages normally, and the slices are more useful for campaigns than one undifferentiated block.
- Export the segment. An export is not paging. It runs against the whole matched set server-side, so a 40,000-row segment comes out in one file without you ever scrolling through it.
Working with big segments in practice
Treat the result table as a sanity check, not as the deliverable. Read the count, spot-check the first pages to confirm the filters are doing what you think, then export. If you are building for outreach you will slice the segment anyway, because a message written for one country and one role always outperforms a message written for 400,000 people.
The same applies through the API and CLI: previews are for checking, exports are for volume.