Behavior When Automation Studio File Drop Conditions Overlap

Cause and System Behavior

• Basic Principle: The Automation Studio File Drop trigger executes only one automation per file uploaded to the FTP site, based on matching conditions.

  • You cannot intentionally trigger multiple automations simultaneously with a single file import.

  • If you need to execute multiple processes, you must separate the files (e.g., upload two distinct files) and configure a corresponding automation for each.

     

• Behavior on Overlap: When a dropped file matches the trigger criteria of multiple active automations, Automation Studio randomly selects one automation to run.

  • This behavior is documented in Salesforce Help under "Automation Starting Sources". https://help.salesforce.com/s/articleView?id=mktg.mc_as_triggered_automations.htm&type=5

  • This can lead to unexpected results, such as the intended automation failing to start or a different automation running than expected.

     

Resolution

To resolve issues where File Drop triggers overlap unintentionally, ensure a strict 1:1 relationship between the file uploaded to the FTP and the automation it triggers.

Follow these steps to correct the configuration:

1. Review Naming Patterns

   • Check the File Drop conditions for all currently active automations.

   • Identify any areas where trigger conditions (specifically file naming patterns) overlap across multiple automations.

   • Update the naming patterns to be unique, ensuring each automation is triggered only by its specific file.

      

2. Deactivate Unnecessary Automations

   • Check for any old automations that remain active, such as those created for past testing or legacy processes.

   • Identify and set any unnecessary automations causing the overlap to Inactive