AutomationEdge Component Startup, Connectivity, and Configuration Failures

Self-Help & Learn
1

Troubleshooting SFTP ‘No Such File’ Error Due to Incorrect Pathing in AutomationEdge.
Problem / Scenario: An AutomationEdge process fails with a “No such file” or “No such file or directory” error during SFTP file upload or folder creation despite a successful SFTP connection and directory listing test.

2

Go to AutomationEdge Process Studio / SFTP Activity Configuration.

  1. Verify the full target path specified in the SFTP activity.
  2. Distinguish between absolute paths (starting with ‘/’) and relative paths (relative to SFTP user login directory). Always prefer absolute paths for explicit directory targeting.
  3. Ensure all intermediate parent directories exist on the SFTP server before attempting file uploads or subfolder creation.
3

Check permissions and path casing.

  1. Unix/Linux SFTP servers are strictly case-sensitive. Verify exact case of all directory and file names.
  2. Avoid duplicate trailing slashes (e.g. ‘//folder//file’).
  3. Pre-validate paths using an SFTP List Files activity before executing file write steps.