# Verify a decision

> Find the recorded decision for an agent action.

Source: https://docs.synkro.sh/onboarding/verify-events

Run `synkro status` first. Confirm the service is healthy, enforcement is active, and your repository has a valid `synkro.lock`. Note the time so you can find this action in the event log.

`synkro status` reports service health. To check your project's Rules and actions,
use the verification commands below.

If you approved connecting your agent through `synkro onboard`, use
`synkro onboard verify` as described in the [Quickstart](/quickstart).
It checks the first Rule and action. For the full event history, use your
signed-in CLI and follow the steps below.
The connected agent can also follow these steps to inspect its own installation;
its results exclude other users' and installations' activity.

## Ask the agent to run a command

In a fresh agent session, send:

```text
Run git status --short in this repository. Do not change any files.
```

Let the agent run it through its command tool so Synkro receives the action.

## Find its decision

```sh
synkro events --type verdict --limit 5 --details
```

Find a new `verdict.created` event. Check its time, session and decision against the command you asked the agent to run. Hosted results include other users and machines in your organization, so the newest event may not be yours.

If the verdict does not include the command itself, copy its `correlation_id` and use it to read the related action:

```sh
synkro events --correlation REPLACE_WITH_CORRELATION_UUID --details
```

Replace the placeholder with the ID from the output.

Read the decision's reason, check status and matching Rules. If it reports paused enforcement or an error, follow [Troubleshooting](/troubleshooting). Use the [tutorial Rule](/guides/rules#test-a-rule) to test a specific match and block.

## If the result is missing

Run `synkro events --limit 10 --json` to see recent activity, then follow [No new decision appears](/troubleshooting#no-new-decision-appears).
