You're looping through every entity/parent combination, and starting a DM job for many of them. This could be spawning hundreds or thousands of threads, each one generating a file, so you're hitting Windows limits somewhere. If your environment is on-premises, you can try tweaking Windows settings, but to be honest this just seems like a flawed approach. Depending on why exactly you're trying to get data out of OneStream, there are better approaches than this bruteforcing.
I agree I was just doing a performance testing on the OS cloud app. Just wanted to check of there is an alternate way/ a setting(scaling) to avoid such long Operation failures on the Database.
