Resolving “Permission Denied” Errors When Writing to SFTP Destinations via Orchestration

The orchestration occasionally fails to deliver due to a permission error when attempting to write to the remote folder on the SFTP server.

Problem

During data egress to an SFTP destination, you may encounter a permission error such as:

Failed to make directory: <folder_path>. Error: Permission denied

This prevents the orchestration workflow from completing successfully.

Cause:
SFTP accounts provided by the platform do not have write access to the root directory. All file operations (create directories, upload files) must occur within the account-specific subdirectory. Attempting to write directly to a root-level path or a folder outside the account subdirectory will result in a permission denied error.

Resolution:

1. Verify the remote folder path configured in the orchestration or data egress destination.

2. Update the path to include the account-specific subdirectory at the beginning.

   • Example: If your SFTP account name is account123 and you want to write to a folder Egress/Data/, set the remote folder path to:

     account123/Egress/Data/
     

3. Save the updated configuration.

4. Retry the orchestration or data egress task.

Preventive Recommendations:

• Always prepend the account-specific subdirectory to any remote folder path in SFTP destinations.

• Do not attempt to write directly to the root directory.

• If multiple accounts are used, ensure each account has a unique subdirectory path configured.