ÃÛ¶¹ÊÓƵ

Documentation

Fix SFTP multi-access ingestion error in ÃÛ¶¹ÊÓƵ Experience Platform

Last update: Tue Jun 03 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

ÃÛ¶¹ÊÓƵ Experience Platform (AEP) fails to ingest data from SFTP when file access policies restrict multiple accesses. To fix this, avoid using the preview feature, configure ingestion settings via API with specific parameters, and verify SFTP credentials and server behavior.

Description description

Environment

ÃÛ¶¹ÊÓƵ Experience Platform (AEP)

Issue/Symptoms

  • Files become inaccessible after ÃÛ¶¹ÊÓƵ Experience Platform (AEP) previews them during SFTP dataflow setup.
  • The system fails to configure the dataflow because it cannot access the files.
  • The issue affects both CSV and JSON files.
  • Preview functionality triggers a download, causing the SFTP server to move or lock the file.
  • File access policies on the SFTP server restrict multiple accesses or downloads.

Resolution resolution

To resolve this issue, follow these steps:

  1. Confirm whether the SFTP setup follows one of these behaviors:

    • Option A: The file becomes temporarily invisible while one connection is active.
    • Option B: The file becomes permanently inaccessible after a single download (this matches the current behavior).

  2. If the setup follows Option B, the AEP UI doesn’t support this workflow. Features like preview and schema inference require multiple file accesses. In this case:

    • Avoid using the Explore endpoint (used for previewing files in the UI) to preview the file.

    • Configure ingestion settings via API with the following parameters:

      • disableChunking: true
      • maxConcurrentConnections: 1

  3. Compare working and non-working connections:

    • Verify whether credentials associated with non-working connections can download files using an external SFTP client, such as Cyberduck or WinSCP.
    • If the file remains inaccessible even when using external clients, check for possible misconfigurations on the SFTP server.

  4. Collaborate with the internal SFTP team to confirm whether exceptions are configured for the affected nodes and ensure no restrictions block multiple accesses.

  5. If another set of credentials works consistently, use them for AEP source connections while you troubleshoot the issue.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f