# Activity log

The activity log is a searchable history of important platform events. Operators use it to understand recent changes, find the source of an unexpected result, and continue work with the right context.

It is not where daily work starts. Start from the product area first: Catalog, Pricing, Distribution, Payments, or Adragent. Use the activity log when you need the history behind what you see there.

## What appears here

| Area                    | Examples                                                                         |
| ----------------------- | -------------------------------------------------------------------------------- |
| **Catalog**             | Property updates, room changes, content edits, image uploads, mapping decisions. |
| **Contracts**           | Drafts, signature status, amendments, expiry changes.                            |
| **Pricing & inventory** | Rate updates, inventory changes, stop-sale changes, restrictions, promotions.    |
| **Distribution**        | Channel setup changes, mapping updates, accepted or failed channel updates.      |
| **Payments**            | Settlement runs, refunds, virtual-card events, chargeback updates.               |
| **Adragent**            | Prepared operations, approvals, expired runs, completed runs, failed runs.       |

## How operators use it

* **Find the source of a calendar value.** A June weekend price is higher than expected; open the related activity and continue to cell history for the exact date.
* **Follow a channel issue.** A channel update failed; find the affected property, channel, and reason before retrying or changing the mapping.
* **Answer a finance question.** A payout looks different from expectation; follow settlement, conversion, refund, or chargeback activity from the booking.
* **Review an Adragent run.** See the request, preview, approval, and result before repeating or adjusting the task.

## Searching

Useful filters include:

* Property, supplier, booking, channel, or payment reference.
* Date range.
* Area such as Pricing, Distribution, Payments, or Adragent.
* Outcome: completed, failed, cancelled, expired, or waiting for follow-up.

Search results link back to the product area where the operator can continue the work.

## Where to next

* **Real-time items that need attention** → [Notifications](/console/notifications-and-ops/notifications.md)
* **Adragent operations** → [Adragent](/console/adragent/overview.md)
* **Cell-level history for rates and inventory** → [Cell history](/console/pricing-and-availability/cell-history.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://adrasis.gitbook.io/console/notifications-and-ops/audit-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.