I am trying to get a solution for a unique exception case of File drop automation.
The scenario is, a file(with wrong data) is dropped into FTP, overwrites a Data extension and waits for 2 hours and then triggers a journey to send out the emails. During this delay of 2 hours, a new file (with correct data) is dropped into FTP within an hour. Here the 1st file drop automation is in progress while the second one waits in the queue.
Is there a way to stop the email triggering from the 1st automation since it had bad data with any automation activity?