> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/system-messages.md).

# System messages

## System messages

System messages inform users about operation results, errors, missing data or the need to confirm an action.

### When they appear

Messages may appear, among others, during:

* incorrect login,
* missing required fields,
* deleting a record,
* blocking or unblocking a user,
* confirming a document,
* importing data from a file,
* date or value conflicts.

### How to react

1. Read the message.
2. Check whether the message requires confirmation.
3. If the message concerns an error, correct the data in the form.
4. If you are not sure, do not confirm the operation and report the issue to an administrator or service desk.

### What to watch for

* Operations such as deleting require particular care.
* A message may indicate that an operation is impossible because of related data.
* During data import, a message may indicate a problem with the file format or import parameters.

### Related pages

* [Adding, editing and deleting records](/aquila-store-user-manual/system-basics/adding-editing-and-deleting-records.md)
* [Data import and export](/aquila-store-user-manual/system-basics/data-import-and-export.md)


---

# 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.aquiladynamics.com/aquila-store-user-manual/system-basics/system-messages.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.