Cornerstone Reporting 2.0: the limits nobody mentions until you hit one

Every month, somewhere, an HR analyst opens Cornerstone Reporting 2.0, rebuilds more or less the same report, waits, downloads a CSV, and pastes it into a deck. It works. It has worked for years. And every month it quietly costs more than it looks.

We have built a lot of reporting on and around Cornerstone, and Reporting 2.0 is genuinely capable – for what it is. But it carries a handful of limits nobody mentions until you hit one, usually with an audience watching. Here they are in daylight, so you meet them on your terms instead of theirs.

The 200,000-row surprise

The default download limit in Reporting 2.0 is 200,000 records. If your report matches more rows than that, the download stops at the limit. For a small team, no problem. For an enterprise transcript or user report, you can walk away with a truncated file and present it as if it were the whole picture.

You can raise the limit – but only up to a hard ceiling of one million records, and only by opening the Snapshots screen and changing it for that report. Cornerstone states it plainly: "the export supports up to 1 million records." So two things worth burning into memory: raise the limit before you trust a large report, and know that 1,000,000 rows is the wall. Past a million matching records, Reporting 2.0 cannot hand you everything in a single report, full stop.

And the preview flatters you. Preview mode shows "1,000 rows of data, which will be randomly selected." That is perfect for checking your columns line up, and useless for sanity-checking a total. What you see in preview is not a representative sample of what you will download – so a report that looks right in preview can still be wrong at the bottom.

Scheduled reports that quietly switch themselves off

Here is the one that catches people. If a scheduled report has not been accessed within the last 30 days by any of its users, Cornerstone automatically disables the schedule. So the weekly compliance report you set up and deliberately forgot – the one whose entire value is that you never have to think about it – turns itself off after a month of nobody opening it. The failure is silent. You find out when someone asks where last week's numbers went.

Delivery has edges too. When a report exceeds 25 MB, Cornerstone stops attaching it and emails a download link instead, good for 21 days. Reasonable behaviour – but it tells you what the feature is really built for: a person receiving a file, not a system receiving data. Scheduling to an inbox or an FTP drop, once or daily or weekly, is a fine model for "email me the headcount every Monday." It is the wrong model for "keep my dashboard, my warehouse, and my BI tool current."

It's a report builder, not a data pipeline

That is the heart of it. Reporting 2.0 is exactly what its name says: a tool for building and running reports a human reads. Point-in-time snapshots, per-report limits, file delivery, manual runs. Used for that, it is good.

The friction starts the moment your need changes from "a report" to "our data, live, everywhere" – a dashboard that is current, a warehouse the whole company queries, a BI tool that refreshes itself, an AI assistant that can answer questions about your workforce. None of those want a 200,000-row CSV that somebody remembered to download. Try to serve them from the reporting screen and you end up maintaining a small museum of workarounds: scheduled exports, a shared mailbox, a script that stitches CSVs, a calendar reminder to re-enable the report that switched itself off.

Cornerstone is already moving the other way

You do not have to take our word that reporting's centre of gravity is shifting. Cornerstone itself calls the Data Exporter API "the spiritual successor to RAPI" and says it will "over time, start to deprecate RAPI endpoints if the same data can be retrieved via DEAPI." The platform's own direction for getting data out points at the Data Exporter, not the reporting screens.

That API has its own sharp edges – rate limits, a data-warehouse lag, a few genuine traps. We wrote those up separately in the Cornerstone Data Exporter API guide, if you are going to build against it directly.

The honest bit

None of this means Reporting 2.0 is bad. It means it has a job, and that job is not "be the live source of truth for your whole organisation." When people ask it to be, the limits above stop being trivia and start being the reason the Monday numbers are late.

That gap is why we built octo.taxi. It syncs your Cornerstone data continuously and gives you dashboards, an org chart, plain-language answers, downloadable reports, a REST API, and a live feed your BI tool can read – so the monthly export ritual, the 200k ceiling, and the schedule that quietly disabled itself simply stop being your problem.

You will still run the occasional Reporting 2.0 report, and that is fine – it is good at what it is for. But your dashboards, your board numbers, and your BI tool should not hinge on remembering to raise a download limit.

Your data should move freely, from A to B, in style.

---

Sources. Cornerstone's own documentation: Reporting 2.0 – Create Report (record limits) · Reporting 2.0 – Delivery and Scheduling · Reporting API considerations (DEAPI as the successor to RAPI).