# Configure reviews

> Choose the activity reviewed by Observations and understand how review windows advance.

Observation reviews assess new agent activity in your project. A project’s review scope determines which activity is assessed together; active [Signals](/docs/platform/observations/signals.md) supply criteria for that assessment. Reviews can also produce findings without active Signals.

[Connect Meta Agent](/docs/platform/meta-agent/investigations.md#connect-meta-agent) before running reviews. Reviews discover recognized [agent invocations](/docs/platform/reference/telemetry.md#agent-runs) in every scope; native CLI spans alone are not eligible.

## Review scope

An owner or admin configures the unit of review in **Settings → Project settings → Observations**, under **Observation reviews**:

* **Agent run** assesses a top-level invocation with its descendants. Use this when the behavior is contained in one agent response.
* **Trace** brings agent activity from the same trace into one review, including work passed between agents.
* **Attribute** collects activity across traces by a shared field such as `session.id`. Use it for a conversation or workflow spanning requests.

For attribute scope, the application must record the grouping field. Activity without it is excluded; value and type affect which records belong together. See [grouping in Logs](/docs/platform/logs/search-and-filters.md#grouping). Save the settings to apply them to subsequent reviews; existing observations retain their original scope.

## Review new activity

Automatic reviews run on an hourly cycle. To request a pass between scheduled reviews, open the **Observations** tab and choose **Run review**. The request checks for new eligible activity; it does not replay the project’s history.

Reviews advance through received activity rather than rescanning all retained telemetry. A project’s first review starts with the UTC hour in which that review runs, with overlap for delayed arrivals. Subsequent windows continue from saved progress. The finding records its evidence window.

To check a new Signal, record representative activity after activating it, confirm that activity appears in Logs, then request a review. Repeatedly pressing **Run review** does not force unchanged evidence to be reviewed again. Check representative matches and non-matches before relying on a criterion; [create a replacement Signal](/docs/platform/observations/signals.md#check-the-results) if its wording is ambiguous.

## When no finding appears

The review result tells you where to continue:

* **Already reviewing this project**: wait for the current pass to finish.
* **Still in cooldown**: retry after the displayed interval.
* **Checked for new activity — nothing new found**: check that new activity arrived in the selected project and falls within the review scope. For attribute scope, inspect the grouping field in Logs.
* A usage or plan notice: an owner can resolve it through [Usage and billing](/docs/platform/administration/usage-and-billing.md).

Confirm the intended Signal is active. If the activity is older than the review window, inspect it directly in Logs instead of expecting a manual pass to replay the project’s history.

Completed findings appear on the **Observations** tab. See [Review findings](/docs/platform/observations/review-findings.md) for reading their assessments and supporting evidence.