Summary
When running an orchestration to send files to a destination, the workflow may fail with a “Permission denied” error. This typically happens when the configured credential does not have sufficient write access to the target folder, even though the connection test may succeed.
Symptoms
Orchestration takes longer than expected or fails.
Error message in the workflow logs similar to:
Failed to upload file to: /<folder>/<filename>.csv.pgp. Error: Permission denied
Cause
The credential being used does not have the required write access to the folder in the destination.
A successful credential test only confirms connection to the destination.
Folder-level permissions are not validated during the credential setup.
Resolution
Verify the folder path being used in the orchestration (e.g.,
/test/).Check the permissions assigned to the credential user for that folder.
Ensure the user has write access in addition to read/connect access.
Update the folder permissions as needed.
Re-run the orchestration after permissions are corrected.
Once the permissions are updated, the workflow should complete successfully.
Additional Notes
Use Version History in Amperity to track recent changes to credentials or destinations.
Always validate both the connection and folder permissions before testing file delivery.
Example Scenario
A customer attempted to send a sample file (100 records) to a new destination. The orchestration failed with:
Failed to upload file to: /test/lahouh_sample_file_v1.csv.pgp. Error: Permission denied
After updating the folder permissions for the credential user, the orchestration ran successfully and completed without errors.