> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clarityq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Daily Discovery Jobs

> How ClarityQ keeps your Event Catalog in sync with the events flowing into your warehouse.

Your product instrumentation isn't static — teams ship new events, deprecate old ones, and add parameters along the way. ClarityQ runs daily discovery jobs against your events table to keep the Event Catalog aligned with what your warehouse actually contains.

## What the Jobs Discover

Each day, ClarityQ scans the most recent window of events in your warehouse and updates the catalog with what it finds:

| Change                       | What Happens                                                                                                                     |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **New event**                | Added in **Pending** approval status, **Active** data status. AI generates a suggested description when it recognises the event. |
| **New parameter**            | Added under the source event, and to the **Common Parameters** tab if it appears on more than one event.                         |
| **New user property**        | Added to the **User Properties** tab.                                                                                            |
| **Updated parameter values** | Distinct values and value counts are refreshed for parameters and user properties.                                               |
| **Updated platforms**        | New platform / version combinations seen for an event are added to its **Platforms** column.                                     |
| **No longer seen**           | Items absent from the recent window flip to **Inactive** data status. Existing entries are preserved — nothing is deleted.       |

## What the Job Runs

Each daily run executes the following, in order:

<Steps>
  <Step title="Fetch changes">
    Scan the events table for new events, parameters, and user properties within the discovery window, and re-calculate which existing items are still active.
  </Step>

  <Step title="Refresh values">
    Update the distinct values and value counts for parameters and user properties. By default, only items missing values are refreshed — ask ClarityQ to switch to a full refresh on every run if you want it.
  </Step>

  <Step title="Suggest descriptions">
    Generate AI-suggested descriptions for any item still missing one — common parameters first, then user properties, then events.
  </Step>
</Steps>

## Where Findings Surface

* **Event Catalog tabs** — New items appear in Events, Common Parameters, and User Properties, with their suggested descriptions pre-filled.
* **Missing-descriptions badge** — The sidebar shows a running count of items still needing a description, leading into the [Missing Description Wizard](/context-layer/event-catalog/missing-description-wizard).
* **Email notifications** — Configured recipients get a daily summary of what was discovered, including new-item counts.

## How to Act on Findings

When the job finds something new:

* **Review** the suggested description, then accept it, edit it, or write your own.
* **Approve** the event, parameter, or user property to move it to **Approved** status.
* **Hide** anything you want to keep out of the catalog and out of the agent's reach.
* **Sync** approved events to the [Semantic Catalog](/context-layer/event-catalog/syncing-events-to-the-semantic-catalog) so the agent can use them.

## Notes on the Discovery Window

<Note>
  The default window is roughly two days. Events that fired before then aren't picked up by daily runs. For a launch event that happened months ago, ask ClarityQ to trigger a one-time backfill against the date range you need.
</Note>

<Note>
  An **Inactive** item isn't gone from your warehouse history — it just hasn't fired during the most recent window. If something flips to Inactive unexpectedly, check whether it was renamed, deprecated, or filtered out by an upstream change.
</Note>