> 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/10.2-data-integration/data-integration-issues/log-table-data-is-not-deleted.md).

# Log table data is not deleted

When you run a job or transformation, data in the log table is not deleted as expected:

* When a job runs, the value in the **Log line timeout (days)** field, along with the **LOGDATE** and **JOBNAME** or **TRANSNAME** fields, which are selected in the **Log table field** pane, determine when to delete the data in the log table. These fields are in the Job properties window in PDI. See [Set up job logging](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/data-integration-perspective-in-the-pdi-client/logging-and-performance-monitoring/set-up-job-logging.md) for details.
* When a transformation runs, the value in the **Log record timeout (in days)** field, along with the **LOGDATE** and **TRANSNAME** fields, which are selected in the **Fields to log** pane, determine when to delete the data in the log table. These fields are in the Transformation properties window in PDI. See [Set up transformation logging](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/data-integration-perspective-in-the-pdi-client/logging-and-performance-monitoring/set-up-transformation-logging.md) for details.

If the name of an existing job or transformation is changed, then any log table entries with the previous name are no longer recognized and are no longer deleted from the table when the **Log line timeout (days)** or the **Log record timeout (in days)** value is present.

If you find that your log table is becoming too large, you should manually purge these unrecognized log table rows using your SQL editor.


---

# 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/10.2-data-integration/data-integration-issues/log-table-data-is-not-deleted.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.
