# Review Decisions and Track Operations
Source: https://docs.chain.link/ace/active-monitoring/guides/review-decisions
Last Updated: 2026-10-05

> For the complete documentation index, see [llms.txt](/llms.txt).

A **decision** is the record Active Monitoring keeps when a monitoring rule matches a risk event for an address on one network. This guide covers four operations: list decisions, open one, resolve or enforce a flagged decision, and track the operation behind an enforced decision. For the outcomes and the evidence a decision keeps, see [Decisions, Review, and Audit Trail](/ace/active-monitoring/concepts/decisions-and-audit).

Most decisions need nothing from you: a **silently logged** decision is a record only, and an **enforced** decision already ran its action. You act on **flagged** decisions, which wait for a person to review the address. You can then resolve the decision, or enforce an action yourself.

## Prerequisites

- Screening is running, and at least one risk event matched a rule. See [Configure the TRM API Key and Screening Schedule](/ace/active-monitoring/guides/configure-screening).
- To resolve or enforce a flagged decision, a signed-in user. These two actions are available in the Platform UI only.
- To use the **API** tab, an ACE API key, sent in the `Authorization: Apikey <API_KEY>` header of each request. See [Create an API key](/ace/getting-started/account-setup#3-create-an-api-key).

## List decisions

## Open a decision

## Resolve a flagged decision

Resolve a flagged decision when you review it and decide that no onchain action is needed. The decision closes, and your reason is recorded with your name.

## Enforce an action on a flagged decision

Enforce an action when you decide that the address needs an onchain action. You choose the function and the values, and Active Monitoring creates the operation on the network of the decision.

## Track an operation

Each enforced decision links to an operation. Its status moves forward until it is final:

| Status                | Meaning                                                                          |
| --------------------- | -------------------------------------------------------------------------------- |
| **Submitted**         | Active Monitoring created the operation.                                         |
| **Sending**           | The operation is being sent to CRE Connect.                                      |
| **Pending signature** | The operation waits for your signer. This status appears only with self-signing. |
| **Executing**         | The operation is signed and executing onchain.                                   |
| **Success**           | The operation is confirmed onchain.                                              |
| **Failed**            | The operation failed. The most common cause is a missing onchain role.           |

In the Platform UI, the status is in the **Operation status** column and in **Operations activity**. In the API, it is in `activity_history` of each enforced action, and `transaction_hash` holds the hash once the transaction is known.

**Pending signature** means your signer must approve the operation before it runs. See [Signing and Ownership Model](/ace/concepts/signing-ownership#signing-in-active-monitoring) for how you sign.

If an operation fails, open the decision. The **Action · Enforcement failed** card shows the CRE Connect operation ID, which you can use to see what happened. Then fix the cause, and enforce the action again from a flagged decision, or wait for the next risk event on that address. See [Troubleshoot Active Monitoring](/ace/active-monitoring/guides/troubleshooting).

## Next steps

- [Troubleshoot Active Monitoring](/ace/active-monitoring/guides/troubleshooting): why a decision is missing, stuck, or failed.
- [Limits, Statuses, and Values](/ace/active-monitoring/reference/limits-and-values): every outcome and status value.