Ungroup Job then Assemble Job does not remember folder structure. Why?

[dhutton]

I have a flow where I want to take a folder submitted by a customer with possible multiple sub folders and multiple different types of files. Sort out the PDF's, create a report, then assemble everything back into the original folder structure. I have used ungroup job and assemble job on other flows to do similar things. When I am doing it this time resulting assembled job has all the individual files in a single folder. What am I missing to be able to have the submitted folder structure be the same after assembling the job?

Flow:

Flow.PNG (26.6 KiB) Viewed 168 times

Starting Folder Structure:

Original Folder Structure.PNG (36.58 KiB) Viewed 168 times

Resulting Folder Structure:

Resulting Folder Structure.PNG (31.42 KiB) Viewed 168 times

[davyverstaen]

Which version of the default elements are you using?

[laurentd]

In Assemble job, use Ungrouped job scheme, with the same Private data key as Ungroup job (by default Ungroup).
AND don't forget to define the right number of subfolder levels.
Default 0 means no hierarchy at all, like in your screenshot.
Increase the value to the desired number of levels, or if you don't know, use a very high number.

[dhutton]

Thanks. I did have the subfolder level set to 0. I have it set to 999 now but I am getting a different error now. When it goes to assemble the job I get the error "Error in line 214 of script : Failed to make directory". The additional information makes it seem that it is likely to be that the path has both / and \ in it.
C:/.../16/Test 16-04_24_2024 - 13_13/001I5_test16\Not Zipped\333'

The switch server (Windows based) itself is using / and then the recreated folder structure is using \. I am not sure how I can fix this as I am using the Automatic job folder name setting.

[dhutton]

Which version of the default elements are you using?

This appears to be the issue.
I was using
Ungroup Job V6.0 (beta)

When I downgraded to V5.0 then everything works as I would expect. I guess there is a bug in V6