Overview
Sometimes an orchestration may appear to run much longer than expected or remain “in progress,” even when sending a very small file.
In many cases, this behavior is caused by insufficient write permissions on the destination folder, even though the credential connection test succeeds.
This article explains how destination permissions can affect orchestration runtime and how to resolve the issue.
Symptoms
You may notice one or more of the following:
Orchestration stays in progress for an unusually long time
Small files (for example, test files with limited records) take much longer than expected
Orchestration eventually fails with a permission denied error
Credential connection tests succeed, but file delivery fails
Destination setup appears correct at first glance
Why This Happens
Credential validation checks only confirm that a connection can be established.
They do not always verify:
Write access to the target folder
Folder-level permissions on the destination
Whether the destination path allows file creation or updates
If the credential does not have write permission on the configured folder, the orchestration may wait and then fail during the file upload step.
Common Error Message
You may see an error similar to:
Failed to upload file. Error: Permission denied
This indicates that the destination rejected the file due to insufficient access rights.
Solution: Verify Destination Folder Permissions
Ensure that the credential used by the destination has write access to the configured folder path.
Steps to Resolve
Review the destination configuration and note the target folder path
Confirm that the credential has:
Write permission
Permission to create or overwrite files in that folder
Update folder permissions if needed
Save the changes
Re-run the orchestration
Once permissions are corrected, the orchestration should complete successfully.
Validation After Fix
After re-running the orchestration:
The workflow should complete normally
The output file should be delivered to the destination folder
No permission-related errors should appear in logs
Best Practices
Always verify folder-level permissions, not only credential connectivity
Test destinations with a small sample file before enabling production workflows
Use version history to track changes to credentials and destinations
If an orchestration is slow or stuck, review destination errors before retrying multiple times
Summary
An orchestration that runs longer than expected or fails when sending a small file is often caused by missing write permissions on the destination folder.
Even if the credential connection test passes, folder access must be explicitly allowed for file delivery.
Verifying and correcting permissions resolves the issue quickly and prevents future failures.
Applies To
Orchestration workflows
Destination configuration
Credential setup
File-based destinations
Sample and production file deliveries