Orchestrator: "Create Document Validation Action" Returning From Server Status 500


I’m having an issue while creating a Document Validation Station Action on a Re-Framework with Studio and Orchestrator 2020.4.1.

I’m Using Document Understanding to Extract Data from some invoices, and based on the output, document categorization and confidence level of the extraction I need to submit the same invoice to manual validation to a human using Action Center’s Document Validation Station.

At First, I was receiving an error when creating the Validation Station action outside of the main workflow as indicated on this forum entry Getting error in wait for form task and resume activity

Later on, after moving all the validation station logic in the main workflow I’m receiving a new error.

Error Message:

"Name": “Create Document Validation Action”,
“Id”: “1.204”,
“InstanceId”: “56”,
“TypeName”: “UiPath.IntelligentOCR.Activities.CreateDocumentValidationAction”

*RemoteException wrapping UiPath.DocumentUnderstanding.Persistence.OrchestratorException: The remote server returned an error: (500) Internal Server Error. *
at UiPath.IntelligentOCR.Activities.BaseOrchestratorClientAsyncActivity.ThrowIfNeeded(Task task,
Boolean suppressThrowException)
at UiPath.IntelligentOCR.Activities.BaseOrchestratorClientAsyncActivity.EndExecute(AsyncCodeActivityContext context,
IAsyncResult result)
at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context,
IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor,

I had the same issue and couldn’t get it to work. Any help will be appreciated!

I am having same issue, please help

Hi @Ioana_Gligan , this was something to do with storage bucket path if I remember. Could you please update if this was resolved in a recent activity pack version or if there is a work around ? thanks

Hello all,

Please try to upgrade the IntelligentOCR package to the latest one and see if the error continues to reproduce. If it does, please send me a workflow that I can reproduce this with so we can log and trace it…

Thank you,