Maestro Process Issue: Document Understanding Output Becomes Null When Passing Data to Agent

Help Maestro
1

Hello,

I need support regarding an issue in my Maestro process.

I have created a Maestro workflow that contains an RPA task using Document Understanding to extract data from documents. The extraction is completed successfully, and I can see the extracted output in the workflow.

However, when I pass the extracted data to an Agent, the Agent receives a null value.

After debugging the flow, I found that the output from Document Understanding takes some time to get updated while the process is running through Maestro. To handle this scenario, I added a condition to check whether the JObject is null. I used the following expressions:

  • var.Jobject == null
  • var.Jobject != null

If the JObject is null, the workflow waits for one minute and then checks again. I also created a separate wait workflow for this purpose. When I run the RPA task independently, the output gets updated in less than one minute, which is why I initially configured the wait time to one minute. I also tried increasing the wait time, but the issue still persists.

Unfortunately, the process keeps running in the loop for a long time and never exits, even though the Document Understanding extraction has been completed successfully.

Has anyone encountered a similar issue in Maestro? Is there a recommended approach to synchronize the Document Understanding output before passing it to the Agent? Also, is there a better way to validate whether the JObject has been updated instead of using the conditions mentioned above?

Thank you.

2

PFA image for your reference

image
image561×340 17.7 KB

3

It doesnt sound right to me that the ‘object takes time to be updated’, it shouldnt resume until its been communicated back.

I’d double check your workflow to ensure its not being passed out as null?

On another note, if this isnt just for learning, you are probably better off just using Studio desktop for this. The long running template there is much better and won’t cost you $1 per job.

4

Hi @QRPABOT

agreeing with Jon, RPA Tasks in Maestro are synchronous, the gateway only gets the token after the task finishes and writes its output to the process variable, so theres no real delay to wait for. If var.Jobject stays null through the whole loop, its not a timing issue, the value was never actually written there, wich also explains the infinite loop

check the RPA Task node itself in the Maestro designer, not the xaml, theres a Data Input/Output mapping panel. The output argument from your workflow needs to be explicitly mapped there to var.Jobject, if that mapping is missing or wrong that would explain it working standalone but coming out null through Maestro

also check the type, if your workflow returns a JObject but the process variable expects a String or the platform’s own Json type, that mismatch can silently resolve to null too

id drop the wait loop, fix the mapping, and test again.

hope this helps