I looked at your project and there are a couple things here. You have the Form Task and Wait inside a loop. You don’t want to do that. What will happen is it’ll suspend the job on the first item in the loop and wait for the action to complete. When the form task is completed it will resume and do the next iteration of the loop. A Document Understanding process should be linear - top down, process one item.
You want a dispatcher automation that creates a queue item for each document. Then a separate performer automation on a queue trigger to take a queue item from the queue and process it - including creating the form task and waiting for it to be completed. Then you set your queue trigger to spawn as many jobs as your licensing can handle, so you end up with as many documents processed - and waiting actions - as you can.
Anyway, the issue with the serialization is your jobject variable (this is a really bad name for a variable, by the way, as jobject is a type. You shouldn’t name variables the same name as a type.) Anyway, you have the jobject variable scoped to Main, and your Wait activity is (of course) also inside that Main scope, so you get the serialization error.
As you can see in this modified project, I have split the steps into separate sequences and changed the jobject variable’s scope to the lowest it can be - the “classify and check confidence” sequence. If you look in the other scope (the “check confidence” sequence) you won’t see that jobject variable because it isn’t scope above that sequence.
Practice.zip (11.9 KB)