Overview
This article describes how to troubleshoot SFTP delivery failures when a single campaign fails to deliver to a third-party destination while other campaigns using the same SFTP destination complete successfully.
In most cases, this is not an Amperity or host-side outage, but a campaign or credential configuration issue.
Symptoms:
One campaign fails SFTP delivery
Other campaigns to the same SFTP destination succeed
Workflow error message:
Auth fail for methods 'publickey,password'
Root Cause:
When only one campaign fails:
The SFTP host is reachable
Credentials work for other campaigns
The failure is typically due to:
A recent campaign edit
A credential mismatch referenced by that campaign
Campaign not picking up the latest credential state
Investigation Steps:
1. Confirm Scope
Identify the failing campaign
Verify other campaigns using the same destination succeed
Confirms this is not a host or infrastructure issue
2. Review Workflow Error
Open workflow run history
Confirm authentication error:
Auth fail for methods 'publickey,password'
3. Check Campaign Version History
Navigate to Campaign → Version History
Look for: Recent edits, Treatment group updates, Destination changes
4. Review Destination Credentials
Go to Settings → Credentials
Verify: Correct username, Correct auth method (public key / password)
Credential hasn’t been partially updated or rotated
Resolution:
One or more of the following typically resolves the issue:
Re-save or update the campaign
Re-validate or update the destination credential
Re-run the workflow
Once corrected, the workflow completes successfully.
How to Tell If This Is Amperity vs Host
| Scenario | Conclusion |
| Other campaigns succeed | Not host issue |
| Auth error returned | Credential/config issue |
| Success after campaign update | Campaign-related |
| No platform-wide failures | Not Amperity infra |
Notes
If the issue persists, collect campaign name, workflow ID, and credential ID. Escalate to Support with orchestration logs for deeper review