How to troubleshoot SFTP product feed delivery failures

First determine whether the file reached the expected destination. Connection or authentication failures happen before parsing; malformed files and product diagnostics happen after delivery. Keeping those stages separate prevents wasted feed edits when the real problem is credentials or file transfer.

Review the SFTP client's exact error and the server-side result if available.

• Hostname and port
• Username and authentication method
• Key or password validity
• Host key changes
• Remote directory and permissions
• Expected filename or pattern
• Transfer completion and file size
• Schedule and timezone

Once delivery is confirmed, check encoding, delimiter or XML structure, compression, headers, row count, and whether the generated file completed before upload began. A partially written file can transfer successfully and still fail downstream.

After fixing delivery, do not stop at a successful SFTP session. Confirm the next Merchant source update processed the expected product count and values, then inspect any remaining product-level diagnostics independently.

Track repeated delivery gaps alongside Merchant-side freshness. CommerceVigil can show when processed product state or diagnostics stop changing as expected, but upstream SFTP logs remain the authoritative evidence for transport failures.