# Your first action

Start a reversible action, follow it, and read what it gave.

## The steps

1. Choose a machine with **nothing at stake**, and check that the **Snapshots** capability is open to you.
2. In **Inventory**, open its panel, or right-click it in the tree. On the **Risks** page, a row's **Act** button opens the same menu.
3. Choose **Take a snapshot**, give it a name, and confirm.
4. Follow the action in the tracking tray, at the top right: it stays with you from one page to the next.
5. Read its outcome, then find it again in **Actions › Action log**.

## What the menu offers

It only shows what is possible: what your locks allow, what the collector can do, and what the machine's state permits. **Start** does not appear on a running machine.

## What happens after your click

1. The request goes into the journal, before it even leaves.
2. Your rights are checked again when it is handed to the collector.
3. The collector re-reads the machine's state. If it has changed, it does not act.
4. The hypervisor executes, and the collector reports back.
5. The screen re-reads the real state: it assumes nothing.

One action at a time per machine: until the first one concludes, a second is refused, naming the one in progress and its author.

## Read the outcome

| Outcome | What it means | What to do |
|---|---|---|
| **Done** | The hypervisor confirmed | Nothing |
| **Refused by the hypervisor** | The account does not have the privilege | Grant it: retrying will not change anything |
| **Never sent** | The command never left, nothing moved | Check the collector, then ask again |
| **No response from the agent** | It left without a report: **the outcome is unknown** | Go and look on the hypervisor before retrying |
| **Not executed** | The machine had changed state, nothing was attempted | Look at the machine and decide again |

> After an action, a risk is never marked fixed by hand: it is re-evaluated at the next collection.

### The action comes back refused

Read the privilege named in the outcome, and grant it to the [action account](/en/act/action-account). Without an action account, Naoshift used the collection account, which cannot write.

### The button I expect is not there

A missing button is an answer: a closed lock, a collector to update, or the machine's state. Go back to [the three locks](/en/act/role-and-locks).

### Should I delete the test snapshot?

Yes: a snapshot uses storage. It is deleted from the same menu, as long as the capability stays open.
