Document API insights data visibility timing

[shawnHartsell]

GitHub Copilot generated this pull request.

Why:

Towards github/api-platform#9650

API Insights data can take several hours to become visible. Documenting that delay sets clear expectations for people investigating recent API activity.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adds the approved expected data visibility timing to the authored API Insights UI guide, including the possibility of longer delays during incidents or unusually high volume.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
organizations/managing-programmatic-access-to-your-organization/viewing-api-insights-in-your-organization.md	ghec	ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Copilot]

Pull request overview

Documents expected API Insights data visibility timing.

Changes:

• Adds the typical 4–6 hour processing delay.
• Notes possible longer delays during incidents or high volume.

Show a summary per file

File	Description
content/organizations/managing-programmatic-access-to-your-organization/viewing-api-insights-in-your-organization.md	Documents API data visibility timing.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Medium

[shawnHartsell]

Closing in favor of github/docs-internal#62398. Per the Docs repository routing policy, internal Hubber content changes should be made in github/docs-internal; the replacement PR carries the identical authored-source change.