> 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/pdia-data-integration/pipeline-designer/working-with-jobs/analyze-job-results.md).
# Analyze job results
You can see how your job performed and if errors occurred by viewing logs and job metrics. After you [Run a job](broken://pages/Bm8c4iLK23obaoLjpSgv), the Logs panel opens with tabs that help you to see how the transformation ran and pinpoint errors.
### Logging
The **Logging** tab displays the logging details for the most recent execution of the job. You can also drill in deeper to determine where errors occur. Error lines are highlighted in red.
### Job Metrics
The **Job Metrics** tab shows statistics for each step in your job including how many records were read, written, caused an error, processing speed (rows per second) and more. This tab also indicates whether an error occurred in your job step. If a mistake occurs, steps that caused the job to fail are highlighted in red.
---
# 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/pdia-data-integration/pipeline-designer/working-with-jobs/analyze-job-results.md?ask=&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.