DU using action centre for validation of multiple invoices one at a time

Help Action Center
,
1

I am trying to validate 3 invoices using DU. i have created create document validation action and looped through multiple invoices. when it encounters wait for document validation action and resume activity the execution is not in resume state it always in running state .In action centre the current invoice is in completed state but the execution stops in the wait and resume

2

Hi @rlgandu ,

Could you maybe let us know what is the Setup / implementation that you have done currently ?

Are you using a Parallel For Each activity? Is the Wait For Resume activity kept together with the Create Document Validation Action activity inside the Parallel For Each ?

Let us know some details of the Design used.

3

No i am using a normal for each activity.it has process one invoice at a single time.

4

@rlgandu

So in your setup do you have a for loop and then a create form task and then a wait for resume in same for loop?

If yes then is the bot not getting suspended after each iteration that is after create form and at wait for resume?

Cheerd

5

Yes I have a for loop and then a create form task and then a wait for resume in same for loop
Yes the bot not getting suspended after each iteration

6

If you could share the workflow or snapshot of your workflow?
Have you enabled the Support Persistence settings? Could you also check if you have kept wait for document validation action and resume activity in main workflow

7

Yes i enabled support persistence

Pic1
Pic1397×655 24.4 KB

pic2
pic2395×722 40.6 KB

pic3
pic3611×717 48.5 KB

8

Why are you setting the below fields in Wait for Document Validation Action and Resume.

  1. Document Path
  2. Document Text
  3. Document Object Model
  4. Automatic Extraction Results
  5. Download Directory Path.

If you are running the process from Orchestrator in Unattended fashion, then only you require those field and also those are output field and you are treating that as input field probably as I see you are using the same variable derived from the previous activities.