Why recovery of interactive transaction is more difficult to deal with than is recovery of batch transactions?

Recovery of interactive transactions is more challenging than that of batch transactions because interactive transactions are often dependent on user input and can be in a mid-state when a failure occurs. This complexity requires maintaining a consistent state across multiple concurrent transactions, which can lead to complications such as lost updates or deadlocks. Additionally, interactive transactions may need to be rolled back to a specific point, complicating the recovery process since the system must manage real-time user interactions alongside data integrity. In contrast, batch transactions are typically processed in isolation and can be more easily rolled back or re-executed without user dependency.