Automation Event-Triggered flow debug tool behavior for Marketing Cloud Next

In Automation Event-Triggered flow, the debug tool rolls back changes to the database and each step is a separate transaction which means each step is separately rolled back. This isolates each action and any record creation dependent of the previous element will not be successful tested. 

As a workaround, create an Autolaunched Flow which is a Core flow type to performs the entire set of database requests that will review the process as a single transaction. Then use this core flow as a subflow within the Automation Event-triggered flow.