---
version: "2026.1.0"
language: "en"
---
# Done

The **Done** building block ends an automation case run in the **done** state, meaning the case is finished but marked as **neither passed nor failed**.

**Important:** If a flow ends without a **PASS** or **DONE** block, Leapwork automatically marks the result as **FAIL**. Include one of these blocks to indicate successful completion.

Fully expanded, the **Done** block shows the following properties:  
![image-20260129-121847.png](https://docs.leapwork.com/__attachments/a_683229073ee624f2dd6bd32001f2c85e990682ac11da541b2b10c56a84358707/image-20260129-121847.png?cb=97ccde8a665bb364a2ccf6b8f50b27a6)

**Note:** The screenshot on this page uses the **Elegance Design** , introduced in **2025.3**. If you are using an earlier version, your layout may look different.

## Quick-start

1. Drag **Done** onto the canvas.

2. Connect the block in the flow and optionally specify the basic parameters required for this block to operate: **Stop message**.

3. Run the flow when it's ready.

## Building block parameters

Parameters  
* **Block header** : The green input connector triggers the block to stop the running case and set it to the **done** state. You can rename the block by double-clicking its title and typing a new name.

* **Stop message** : Defines a message that is logged when the case is put in the done state. The message can include tokens from **Text fields** . To insert tokens, right-click the message field and select **Insert token** .

* **Text fields** : Stores key--value pairs that let you use external values in the **Stop message** . To use a field value in the message, right-click **Stop message** , choose **Insert token** , and insert the relevant field name.

* **Add field** : Adds a new field that can be used as a token in the **Stop message**.

## Resources

|                                                **Topic**                                                |                                                  **Description**                                                  |
|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
| [Flows FAQ](https://docs.leapwork.com/faq/latest/leapwork-flow-faq/flows-faq.md)                                                 | Common questions about creating, running, and managing flows in Leapwork.                                         |
| [Flows Troubleshooting](https://docs.leapwork.com/troubleshooting/latest/leapwork-flow-troubleshooting/flows-troubleshooting.md) | Guidelines and solutions for identifying and fixing issues that occur when building or running flows in Leapwork. |