> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/server-control/tools/cut-memory-file.md).

# Cut Memory File

### Cut Memory File

The Cut Memory File option reconstructs the day to find any errors in case of Back-Office problems. The Back-Office uses the memory file to find errors. The memory file is a log of all transactions that occurred during the day at the workstations. If the Back-Office finds an error, this option stops the memory file just prior to when the error occurred. Then the Back-Office allows reconstruction of the day up to the point where the error occurred. Enter in the Stop position field the position in the history file from where you want to rebuild the data.

{% hint style="info" %}
NOTE: only perform this function under the supervision of a PayFacto Software Support Specialist.
{% endhint %}

**Memory File Size**

This field displays the total size of the memoire file.

**Position of the Previous Error**

This field displays the position number of the last error log during the memoire file reconstruction.

**Reconstruction up to the Error**

This field displays the percentage of valid data up to the last error.

**Stop Position**

Enter here the position number to which you want to reconstruct the day.


---

# 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.maitredpos.com/maitred/maitred-online-help-contents-by-module/server-control/tools/cut-memory-file.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.