---
title: Troubleshoot transforms
description: Use the information in this section to troubleshoot common problems. If you encounter problems with your transforms, you can gather more information from...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/troubleshoot/elasticsearch/transform-troubleshooting
products:
  - Elastic Cloud Serverless
  - Elasticsearch
applies_to:
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available
---

# Troubleshoot transforms
Use the information in this section to troubleshoot common problems.
<tip>
  If you can't find your issue here, explore the other [troubleshooting topics](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/troubleshoot) or [contact us](/elastic/docs-content/pull/5399/troubleshoot#contact-us).
</tip>

If you encounter problems with your transforms, you can gather more information from the following files and APIs:
- Lightweight audit messages are stored in `.transform-notifications-read`. Search by your `transform_id`.
- The [get transform statistics API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-get-transform-stats) provides information about the transform status and failures.
- If the transform exists as a task, you can use the [task management API](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) to gather task information. For example: `GET _tasks?actions=data_frame/transforms*&detailed`. Typically, the task exists when the transform is in a started or failed state.
- <applies-to>Elastic Cloud Serverless: Unavailable</applies-to> The Elasticsearch logs from the node that was running the transform might also contain useful information. You can identify the node from the notification messages. Alternatively, if the task still exists, you can get that information from the get transform statistics API. For more information, refer to [Elasticsearch log4j configuration](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed).