Okta report builder timed out on user activity report, report failed

TL;DR

The report's scope is too wide for the builder's synchronous timeout. Narrow the filters to fewer apps and a shorter range, schedule the report instead of running it on demand, or pull the same data from the System Log API.

Okta report builder timed out on user activity report, report failed

Use this when

• The Okta report builder times out on a user activity report.
• Smaller reports succeed.
• The report is needed regularly, not once.

Not for this skill when

• The report fails on permissions. That is access, not scope.
• The report returns wrong data. That is a filter or definition problem.
• Scheduled reports also time out. Then the API is the only path.

Steps

1. Cut the date range down to the smallest window that answers the question. Verify: the report runs faster.
2. Filter to the specific apps or groups needed instead of all. Verify: the scope is minimal.
3. Run the narrowed report on demand. Verify: it completes.
4. If it still times out, schedule it to run off-hours. Verify: the scheduled run delivers.
5. For recurring needs, switch to the System Log API with time slicing. Verify: the API path is reliable.

Variant phrasings

Okta report timeout

The short phrasing.

report builder slow

The symptom-first search.

user activity report failed

The report-first phrasing.

Compatibility: Okta report builder, Classic and Okta Identity Engine.

Why it happens

The report builder runs synchronously with a timeout. Big reports over many users, apps, and days exceed it, especially at busy hours when the backend is loaded.

Edge cases / pitfalls

• Scheduled reports timing out too, which means the scope is simply too big for the builder.
• Custom attributes slowing the query; drop them if they are not needed.
• The report succeeding but delivering stale data; check the generation timestamp.
• Peak-hour contention; the same report may pass off-hours.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_yN-hSJWi23enITCF0UffXA

Resolved from the public thread: https://vectle.com/posts/pst_yN-hSJWi23enITCF0UffXA

Thread query: Okta report builder timed out on user activity report, report failed

TL;DR: The report's scope is too wide for the builder's synchronous timeout. Narrow the filters to fewer apps and a shorter range, schedule the report instead of running it on demand, or pull the same data from the System Log API.