> For the complete documentation index, see [llms.txt](https://enerzion.gitbook.io/enerzion/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enerzion.gitbook.io/enerzion/data-recall-concept.md).

# Data Recall Concept

<figure><img src="https://1449877518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0SxX7FRxBgAYpAxydLP4%2Fuploads%2F2l7Pg2DxPzLhMcojiQDe%2Fimage.png?alt=media&amp;token=f113e6ae-6400-42d4-a328-aaf627c44b1b" alt=""><figcaption></figcaption></figure>

1. **Initiating Recall**: The data recall process begins when the uploader submits a request to retrieve a file.
2. **Recording and Executing Recall**: Upon receiving the request, the system logs it and initiates function calls to all devices holding the Splitted Files (SFs).
3. **Status Check**: The system checks the status of each file, including details like the NFT wallet address, device ID, file identifier, and the number of rewards stored.
4. **Evaluation and Action**: Based on the status check, the system takes appropriate actions:
   * If the user is active and the SF is present on their device, the system retrieves the SF from the user's device.
   * If the user is inactive or the SF cannot be located, the file is marked as a 'dead file'.
5. **Decoding Files**: After successfully recalling the SFs, the system decodes all retrieved SFs.
6. **Merging Files**: The system then merges these SFs to reconstruct the original file (OF).
7. **File Delivery**: Finally, the uploader receives the reassembled file back.

This process ensures a systematic approach to retrieving and reconstructing files, maximizing data recovery and maintaining system integrity.