Why is my report stuck on "Getting Data"?

If a report is showing the status "Getting Data," here's what that means and what to check.

What "Getting Data" means

"Getting Data" is a normal, in-progress status. It means NinjaCat is actively pulling the data your report needs — the request is either queued or running on our side. For definitions of all report statuses, see Report Status Meanings.

"Getting Data" is not an error status. If a report has actually failed, you'll see a separate error state (for example, "Error Getting Data") rather than "Getting Data."

Why it can take a while

A report can stay in "Getting Data" for a number of reasons, including:

• First-time or historical data loads. Pulling a large date range or loading data for the first time takes longer than a routine refresh.
• Temporary limits from a data source. If one of your connected platforms is temporarily rate-limiting requests, NinjaCat automatically pauses and retries that portion of the data pull. When you see a progress indicator like "Getting Data (2 of 5)," it means some data requests are still completing. These paused requests resume on their own — you don't need to do anything.
• Queued work on our side. During busy periods a request may wait briefly in the queue before it starts.

In most cases the report will finish on its own once the data pull completes. If you see a progress count, it's working through the remaining requests.

What you can do

• Give it time, especially for a first-time load or a large date range — these legitimately take longer.
• Check that your data sources are connected. If a connection has expired or lost access, the underlying data pull can't complete. See Update Data Source Tokens.

When to contact support

If a report stays on "Getting Data" for an unusually long time with no progress, or it never completes, contact NinjaCat support at [email protected]. A genuinely stuck report is something our team resolves on the back end — it isn't something you can force to complete yourself.

Note: NinjaCat does not publish a fixed time limit or SLA for how long "Getting Data" should take, because it depends on the size of the data pull and the responsiveness of the connected data sources. Use "no progress for an unusually long time" as your cue to reach out to support.