# Run a job
After you create a job and configure its properties, you can run the job. You can control how the job runs without modifying the job itself by configuring run options before running the job.Run a job by completing steps in the following sections:
1. Log into the Pentaho User Console.
2. Open **Pipeline Designer**:
* If you are using the **Modern Design**, in the menu on the left side of the page, click **Pipeline Designer**.
* If you are using the **Classic Design**, click **Switch to the Modern Design,** and then in the menu on the left side of the page, click **Pipeline Designer**.
**Pipeline Designer** opens with the **Quick Access** section expanded.
3. In the table at the bottom of the screen, select either the **Recently opened** or **Favorites** tab.
4. Open the job:
1. Search for or browse to the job, and then click **Open**.
2. Click **Open files**, and then in the **Select File or Directory** dialog box, search for or browse to the job and click **Open**.
5. In the **Canvas Action** toolbar, click the **Run** icon and select one of the following options:
1. To run the job, select **Run**.
2. To run the job with run options, select **Run Options,** and then in the **Run Options** window, configure options and click **Run**. For details about run options, see [Job run options](https://app.gitbook.com/o/PtpmPYUKgAsUWgv8SVUt/s/dbSFXbJFiObHB299lSSa/pipeline-designer/working-with-jobs/run-a-job#job-run-options).
The job runs and the **Preview** panel opens with the **Logging** tab selected.
**Note:** For information about stopping the job while it is running, see [Stop transformations and jobs](https://app.gitbook.com/o/PtpmPYUKgAsUWgv8SVUt/s/dbSFXbJFiObHB299lSSa/pipeline-designer/managing-transformations-and-jobs/stop-transformations-and-jobs).
### Job run options
| | |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Select configuration** | All jobs are run using the **Pentaho server** configuration. |
| **Clear log before running** | Indicates whether to clear all your logs before you run your job. If your log is large, you might need to clear it before the next execution to conserve space. |
| **Enable safe mode** | Checks every row passed through your job and ensures all layouts are identical. If a row does not have the same layout as the first row, an error is generated and reported. |
| **Gather performance metrics** | Monitors the performance of your job execution. You can view performance metrics in the Pentaho Data Integration client. For details see [Use performance graphs](https://docs.pentaho.com/pdia-data-integration/data-integration-perspective-in-the-pdi-client/logging-and-performance-monitoring/monitor-performance/use-performance-graphs). |
| **Log level** | Specifies how much logging is performed and the amount of information captured:
- Nothing: No logging occurs.
- Error: Only errors are logged.
- Minimal: Only use minimal logging.
- Basic: This is the default level.
- Detailed: Give detailed logging output.
- Debug: For debugging purposes, very detailed output.
- Row Level (very detailed): Logging at a row level, which generates a lot of log data.
Debug and Row Level logging levels contain information you may consider too sensitive to be shown. Consider the sensitivity of your data when selecting these logging levels. See the Administer Pentaho Data Integration and Analytics guide for instructions on how best to use these logging methods.
|
| **Expand Remote Job** | Bundles all required files for a job, including its sub-components, so they can be sent to a remote server for execution. The remote server runs the complete job without needing to retrieve additional files from the original environment. |
| **Start job at** | Specifies the step where the job begins execution. By default, execution begins at the **Start** step. |
| **Parameters** | Applies parameter values pertaining to your job during runtime. A parameter is a local variable. For more details, see [Parameters](https://app.gitbook.com/o/PtpmPYUKgAsUWgv8SVUt/s/dbSFXbJFiObHB299lSSa/pipeline-designer/managing-transformations-and-jobs/run-modifiers#parameters). |
| **Variables** | Applies temporary values for user-defined and environment variables pertaining to your job during runtime. For more details, see [Variables](https://app.gitbook.com/o/PtpmPYUKgAsUWgv8SVUt/s/dbSFXbJFiObHB299lSSa/pipeline-designer/managing-transformations-and-jobs/run-modifiers#variables). |
| **Arguments** | Applies a named, user-supplied, single-value input given as a command line argument when running the job manually or with a script. Arguments are handled according to a job's design. If the job is not designed to handle arguments, nothing happens.Typically, argument values are numbers, words (strings), or system or script variables. Each job can have a maximum of 10 arguments.For more details, see [Arguments](https://app.gitbook.com/o/PtpmPYUKgAsUWgv8SVUt/s/dbSFXbJFiObHB299lSSa/pipeline-designer/managing-transformations-and-jobs/run-modifiers#arguments). |