> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Objectives of Reality

> Search from the designated node, validate the candidate's suitability, and apply the target in Flow.

In **Flow Studio → REALITY** targets search tasks and found candidates. Configuring a specific connection begins in the Flow input or transit node constructor.

## Search and choice

1. Open the block on the canvas, select a physical node, and set up REALITY. Save the current settings before launching the search.
2. Set the available search area and review the task score.
3. Run a search from the node you select, and the result relates to the node's network path, not the operator's computer.
4. Select a candidate and perform a separate suitability check.
5. Use the target in the configuration only after a successful up-to-date validation and go through the usual Flow application.

Finding an address, a successful TCP connection, and even a TLS response are not equal to permission to use a target. The library separately shows search results, validation status, freshness, and anchorability. Archived or outdated results should not be considered relevant.

## If the target isn't fit

Read the reasons for failure, check the selected node, address, SNI and transport parameters. job cancellation and candidate archiving are part of the search directory; they do not switch an already running Flow to another target.

A pre-use check can detect a changed availability of the target, in which case update the data or select another validated option, then revisit the plan.

## Verification

Make sure that the candidate is tested from the node that participates in Flow, the information is not outdated and the configuration has been successfully used.

## Rollback

Before applying, return the draft settings. After applying, restore the working [version of Flow](https://docs.axottle.com/en/connection-units/lifecycle.md#откат). Archiving the library record does not roll back the deployed configuration.

Features depend on the installed build; the record does not announce the release.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.