---
schema_version: "1"
id: 8956c3924aadf5fc614e90686f0fd37d3f8bbbe13e7485f8eba1aae53fee4158
title: Tracking Policy Operations in the Activity Log
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/general/exp-policies-activity-log.md
canonical_url: https://docs.mulesoft.com/general/exp-policies-activity-log
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 35d8abdefa5b30ded444f6a3d5b2837e47b207faccd81d2f2b247b722aa4c8d7
description: MuleSoft Documentation Site
latest: true
---
---
product: Getting Started
keywords: activity log, policy operations, asynchronous operations, policy status, api manager, anypoint platform
---

# Tracking Policy Operations in the Activity Log

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Every policy change on an external provider runs asynchronously, so a request that Anypoint accepts
isn’t the same as a policy that’s applied on the gateway. Use the **Activity log** tab on an API
instance to confirm what actually happened.

> [!NOTE] Automate policy operation status checks using the MuleSoft MCP Platform Server. For
> details, see
> [get\_policy\_operation\_status](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools-platform#get-policy-operation-status)
> in the MuleSoft MCP Platform Server Tool Reference.

## Before You Begin

Before getting started, make sure you have:

- An Anypoint Platform account.

- Access to the API instance whose **Policies** and **Activity log** tabs you want to view.

  For more information, see [Enhanced Experience Permissions](https://docs.mulesoft.com/general/exp-home-start#permissions).

## Asynchronous Operations and Eventual Consistency

When you trigger a policy action, Anypoint accepts the request immediately and does the real work in
the background: it talks to the provider, refreshes its view of the provider’s state, and records
the outcome. As a result, the policy list is eventually consistent, it sometimes doesn’t reflect the
change right after an action. The UI shows an optimistic view until the background job finishes and
the state is reconciled.

## Reading the Activity Log

The **Activity log** tab lists recent policy operations for the API instance. By default, it shows
the last 10 activities from the last 30 days. Select **Refresh** to reload. If no operations have
run in that window, the tab indicates that there are no recorded policy changes.

Each entry has these columns:

- **Action**: the type of operation, such as **Apply**, **Update** (edit), **Toggle**
  (enable/disable), **Remove**, or **Open** (an open policy apply).

- **Policy**: the policy the operation applies to.

- **Status**: one of three states:

  - **Running**

  - **Completed**

  - **Failed**

Open an entry to see when it started and finished.

## Interpreting a Failure

For a failed operation, open it to see why. The failure detail explains the error and, when
applicable, whether the operation is safe to retry:

- Transient failures come from a temporary problem, such as an unreachable gateway or a scan error.
  Try the operation again.

- Other failures come from your configuration or the instance’s state. For example, an invalid
  configuration, a conflict with the instance’s current state, or a policy that can’t be translated
  for the target gateway. Fix the underlying issue before retrying.

## See Also

- [Managing Policies on Gateway Providers](https://docs.mulesoft.com/general/exp-policies-overview)

- [Applying and Managing Policies](https://docs.mulesoft.com/general/exp-policies-apply-manage)

- [Open Policies](https://docs.mulesoft.com/general/exp-policies-open)

- [Provider Support and Limitations for Policies](https://docs.mulesoft.com/general/exp-policies-provider-reference)