> 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/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](/pdia-data-integration/archived-merged-pages/transforming-data-with-pdi-archive/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](/pdia-data-integration/archived-merged-pages/transforming-data-with-pdi-archive/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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pentaho.com/pdia-data-integration/data-integration-issues/log-table-data-is-not-deleted.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.