> For the complete documentation index, see [llms.txt](https://docs.finout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finout.io/user-guide/optimize/findings-beta/finding-lifecycle-beta.md).

# Finding Lifecycle \[Beta]

Every finding moves through a defined set of statuses, and Finout automatically keeps findings in sync with what your agents find on each daily run — deduplicating repeat findings, and closing fixed ones.

### Statuses

| Status          | Meaning                                                            |
| --------------- | ------------------------------------------------------------------ |
| **Open**        | A new finding, not yet worked                                      |
| **In Progress** | Someone is actively working the finding                            |
| **Fixed**       | The underlying resource is no longer flagged                       |
| **Dismissed**   | A user has explicitly dismissed the finding as not worth acting on |

### How findings are created and matched

Each finding is identified by its resource, and agent. When an agent runs — once a day — it uses this identifier to decide whether to create a new finding or update an existing one:

* If no **Open** or **In Progress** finding exists for that identifier, a new finding is created with status **Open**.
* If an **Open** or **In Progress** finding already exists for that identifier, the existing finding's **Last detected** date is refreshed, it's details are updated, and its status is left unchanged.
* If the most recent finding for that identifier is **Fixed** and the agent flags the resource again, a **new** finding is created rather than reopening the old one.
* If the most recent finding for that identifier is **Dismissed** no finding is created.

{% hint style="info" %}
**First detected** stays fixed at the finding's creation date. **Last detected** updates every time an agent run confirms the same finding, or when a snoozed finding reopens.
{% endhint %}

{% hint style="warning" %}
When a user tries to move a finding from **Fixed** to any other status first checks whether a new finding has already been opened for the same identifier. If one has, the change is blocked, with a note pointing you to the newer finding — this stops you from reopening a stale finding while a current one already reflects the resource's real state.
{% endhint %}

### FAQs

**If I dismiss an finding and the resource is flagged again tomorrow, what happens?** Nothing, the finding won't be updated and no other finding will be created.

**What happens if I mark an finding as Fixed, but the resource wasn't actually fixed (shut down or resized)?** On the next daily run, the agent finds the resource still matches and opens a new finding for it. The original finding stays Fixed and is not updated anymore.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.finout.io/user-guide/optimize/findings-beta/finding-lifecycle-beta.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.