🧡 Skip to main content🔍 Skip to search
Event icon · error

This Error Event is part of FTP & Cloud Actions.

Error · No name…

"Name has not been provided"

Overview

The error message indicates that the Action failed due to an empty input. A filename or directory path was not provided to the Action.

Event examples

See some examples of the Name has not been provided Event messages:

  • Task "Remove Inactive Users" Action "Clear Remote Directory" directory name has not been provided. The filename, directory name, or volume label syntax is incorrect. [os:123]
  • Action "Ensure Remote Directory" directory name has not been provided.
  • Action "If Remote Directory" directory name has not been provided.
  • Action "If Remote File" directory name has not been provided.
  • Action "Wait for Remote Directory" directory name has not been provided.
  • Action "Wait for Remote File" filename has not been provided.

Solution

When using dynamic variables to provide the file or directory name, ensure that the variable is not empty and contains a valid text string (the full path to a filename or directory). If using variables from Triggers and the Task is started manually, all variables from Triggers will be empty, potentially causing this error.

Actions

How seamless automation works? A 90-second demo.

Need assistance?

If you have any questions, please do not hesitate to contact our support team.