# Pipeline Run Configurations
### Description
Run configurations decouple the design and execution phases of Hop pipeline development. A pipeline is a definition of *how* data is processed, a run configurations defines *where* the pipeline is executed. Hop comes supports a number of different runtime engines, each of which will be described in more detail in this section. Each run configuration comes with its own set of parameters and configuration options, all of which are stored as Hop Metadata.
### Choosing a Run Configuration
When starting a new pipeline click **New** next to 'Pipeline run configuration'. All run configurations have a name, description and an engine type, each engine type has its own set of configuration options.
Once created, run configurations are available from the 'Pipeline run configuration' list and are ready to use.
### Options
#### Main Tab
The main tab contains the name, description and the dropdown list for the available engine types.
| Option | Description |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | The name you want to use for this pipeline run configuration. |
| Description | A description you want to use for this pipeline run configuration (optional). |
| Execution information location | The [execution information location](/data-shaper-1.21/knowing-the-data-shaper-designer/index-2/execution-information-location.md) to use with this pipeline run configuration. |
| Execution data profile | The [Execution data profile](/data-shaper-1.21/knowing-the-data-shaper-designer/index-2/execution-data-profile.md) to use with this pipeline run configuration. |
| Engine type | The available engine types are:
|
{% hint style="info" %}
Tip: Check the [Beam Capability Matrix](https://beam.apache.org/documentation/runners/capability-matrix/) to help you decide which Beam engine works best for your pipeline.
{% endhint %}
#### Variables Tab
This tab allows Hop developers to specify a set of variables to be used in the run configurations.
| Option | Description |
| ------------- | ---------------------------------------------------------------------------- |
| Variable name | A variable name. |
| Value | The variable value. |
| Description | A description for the variable. The description is optional but recommended. |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.primeur.com/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/pipeline-run-configurations.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.