> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/obsluga-wnioskow-porzuconych.md).
# Handling abandoned requests
{% hint style="info" %}
Availability of functionality depends on the license and may not be available in all deployments.
{% endhint %}
Abandoned application handling is a feature that allows you to indicate the process that should start when a user abandons an application.
{% stepper %}
{% step %}
#### Select the abandoned application handling icon
To indicate the process that should start after an application is abandoned in Eximee, while in edit mode in the tab **Steps** click the icon **Abandoned application handling**.
Figure 1. View in the Steps tab
{% endstep %}
{% step %}
#### Enter the process name
A panel will expand on the left **Abandoned application handling**. In the text field **PROCESS NAME** enter the name of the process that is to be started after the Eximee application is abandoned by the client. Then the form data will be saved in Formstore and marked as an abandoned application (status ABANDON).
Figure 2. Abandoned application handling panel
{% endstep %}
{% endstepper %}
{% hint style="info" %}
The variable is passed to the process `modelInstanceId`, so it is possible to use the data model in script tasks. Variables can be passed to the process in the same way as to the process started after saving the application: [https://docs.eximee.com/budowanie-aplikacji/proces-biznesowy/przekazywanie-danych-do-procesu](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/przekazywanie-danych-do-procesu.md)
{% endhint %}
| demoAbandon\_app |
| ---------------- |
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/obsluga-wnioskow-porzuconych.md?ask=&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.
