Thanks for the response it doesn't seem to be any of the above as the scenario will force consolidate in about a 1/4 of the time. Its only on that first run following the copy. It's almost like OneStream is performing extra consolidation steps on the initial consolidation. Maybe building out data units records?
Ah, ok, if you're seeing a different performance with a Force Consolidate on the target scenario, it's probably the DU status check that PeterFu mentioned. We state this in training too: if you have 12 months already impacted, Force Consolidate will be faster than a regular Consolidate because it will skip the status check.
So your solution would be to use Force on the first consolidation too.
