I set up an automation that is triggered by a filedrop. When the file is dropped, it should be imported into a data extension. Also, when the automation runs, it kicks off a journey.
I've tested it multiple times and the filedrop has triggered the automation.
This morning, we went live and the filedrop did not trigger the automation. The automation was Active and waiting. The correct trigger file was in the correct directory with the correct naming pattern. I removed that trigger file from our FTP and then re-dropped the exact same file myself and the automation was triggered with no errors.
Has anyone experienced this? Is there potentially some problem with the way we are setting up the drop to the FTP?