You are editing a SQL Server Integration Services (SSIS) package that contains three Execute SQL tasks and no other tasks. The package and all three Execute SQL tasks have their TransactionOption prop

Moving tasks into a Sequence container does not create a transaction unless the Sequence container's own TransactionOption is also set to Required, so this change alone has no effect on rollback behavior.

A Foreach Loop container is used for iterating over a collection, not for wrapping tasks in a shared transaction, and does not cause all three tasks to participate in a single rollback.

Setting each Execute SQL task's TransactionOption to Required causes each task to create its own separate transaction, meaning each task rolls back independently rather than all three rolling back together as a unit.

When a package's TransactionOption is set to Required, the package starts a new distributed transaction and all child tasks with TransactionOption set to Supported automatically enlist in that same transaction. If any of the three Execute SQL tasks fail, the entire package-level transaction is rolled back, undoing all three tasks' changes as required.