> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/advanced-compliance-monitoring-acm/advanced-compliance-monitoring-acm-data-export/troubleshoot-acm-data-exports.md).

# Troubleshoot ACM data exports

{% hint style="success" %}
**Access Type**: Marketplace Manage - Editor

**Premium Feature**: Advanced Compliance Monitoring & ACM Data Exports
{% endhint %}

Advanced Compliance Monitoring (ACM) data export enables organizations to automatically export  compliance monitoring data to external cloud storage platforms or secure SFTP servers. In this article, we will cover some common issues that your organization may encounter when configuring the ACM data export:

* [Connection test failure](#connection-test-failure)
* [Missing export files](#missing-export-files)
* [Authentication errors](#authentication-errors)

***

### Connection test failure

In the case of a connection test failure when configuring or editing the ACM data export, confirm/check that these common issues are not the cause:

* Verify credentials are correct and not expired
* Ensure destination bucket/container exists
* Check that permissions allow write access
* Verify network connectivity if using SFTP

### Missing export files

In the case where your organization is missing an ACM export file, confirm/check that these common issues are not the cause:

* Verify destination path configuration
* Ensure sufficient storage space at destination

### Authentication errors

In the case where there is an authentication error when connecting to your configured export destination, confirm/check that these common issues are not the cause:

* Refresh expired credentials
* Verify STS role permissions and trust policies (AWS)
* Check SFTP server connectivity and credentials
* Validate bucket access permissions


---

# 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.didomi.io/advanced-compliance-monitoring-acm/advanced-compliance-monitoring-acm-data-export/troubleshoot-acm-data-exports.md?ask=<question>&goal=<endgoal>
```

`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.