> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/pipeline-designer/working-with-jobs.md).

# Working with jobs

Create, configure, and then run jobs to orchestrate ETL activities. After running a transformation, analyze its results to identify possible improvements or problems.

* [Create a job](https://docs.pentaho.com/pba/pipeline-designer/working-with-jobs/create-a-job.md)

  Create a job to coordinate resources, execution, and dependencies of an ETL activity.
* [Edit job properties](https://docs.pentaho.com/pba/pipeline-designer/working-with-jobs/edit-job-properties.md)

  Job properties control how a job behaves and how it logs what it is doing.&#x20;
* [Run a job](https://docs.pentaho.com/pba/pipeline-designer/working-with-jobs/run-a-job.md)

  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.
* [Analyze your job results](https://docs.pentaho.com/pba/pipeline-designer/working-with-jobs/analyze-job-results.md)

  After running a job, see how it performed, if errors occurred, and explore the data by viewing the logs.&#x20;
* [Job steps in Pipeline Designer](https://docs.pentaho.com/pba/pipeline-designer/working-with-jobs/job-steps-in-pipeline-designer.md)

  Steps extend and expand the functionality of jobs. You can use the following steps in Pipeline Designer.


---

# 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.pentaho.com/pba/pipeline-designer/working-with-jobs.md?ask=<question>&goal=<user_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.
