Core Data - Best practice to create standlone or temporary objects?

What is best practice to create standlone or temporary objects. I am working on an app and I have user entity. I am performing some background operations on data. These background operations can save the managed object context also. If in between any other object of same context is changed than it is also getting saved which should not happen. If user press cancel than I want to discard the changes.

I have already face this problem many times and asked others also. But not find any consisten answer. What is best practice to create temporary managed object without any context.

If you have multiple, independent background operations running, why are you trying to have them all operating on (and saving their data directly to) the same managed object context? You're taking your independent background operations and making them no longer independent when you do that.

Core Data - Best practice to create standlone or temporary objects?
 
 
Q