The **Execution Input** block is used inside sub-flows to define where the execution should begin when the sub-flow is called. It acts as the starting point and connects to the first functional block within the sub-flow.

When a sub-flow is invoked, the flow begins at the **Execution Input** block and continues through the connected logic path.

The Execution Output block shows the following properties:

**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 **Execution Input** onto the sub-flow canvas.
2. Connect the output of the **Execution Input** block to the block that should receive the execution input within the sub-flow.
3. Run the main flow that references this sub-flow.

## Building block parameters

**Execution Input**

Defines the execution entry point for a sub-flow. Should be connected to the block that will receive the execution input. Enables control to pass into the sub-flow when triggered from a parent flow.

## Resources

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