InvokeOpenFlow: wait for complete not working

Issues and feature requests
1

OpenRPA version: 1.4.57.8
OpenFlow version: 1.5.9
Using app.openiap.io or self hosted openflow: both
Error message: While performing some flow tests, I noticed that InvokeOpenRPA waited correctly if the option to wait until completion was selected. InvokeOpenFlow, on the other hand, does not work, it waits forever, it triggers the bookmark only once, and if it is still idle, it does not try again. AssignOpenFlow does not load the list of flows, it displays errors in the log, and when forcing a specific ID, the same thing happens as InvokeOpenFlow.
Am I missing something?

[
{
“id”: “01aeabf6503a473f”,
“type”: “workflow in”,
“z”: “43d9b8783e1eaa19”,
“queue”: “Form com Payload”,
“rpa”: true,
“web”: true,
“exchange”: true,
“name”: “”,
“x”: 120,
“y”: 300,
“wires”: [
[
“727c4ee40718831b”
]
]
},
{
“id”: “727c4ee40718831b”,
“type”: “switch”,
“z”: “43d9b8783e1eaa19”,
“name”: “”,
“property”: “payload.texto”,
“propertyType”: “msg”,
“rules”: [
{
“t”: “null”
},
{
“t”: “empty”
},
{
“t”: “else”
}
],
“checkall”: “true”,
“repair”: false,
“outputs”: 3,
“x”: 290,
“y”: 300,
“wires”: [
[
“7782813d2880ae5a”
],
[
“7782813d2880ae5a”
],
[
“8a8d018611ec14ef”
]
]
},
{
“id”: “7782813d2880ae5a”,
“type”: “workflow out”,
“z”: “43d9b8783e1eaa19”,
“name”: “”,
“form”: “66c4a652eee029afe4b36404”,
“state”: “idle”,
“removestate”: false,
“x”: 490,
“y”: 280,
“wires”: [

]
},
{
“id”: “8a8d018611ec14ef”,
“type”: “workflow out”,
“z”: “43d9b8783e1eaa19”,
“name”: “”,
“form”: “”,
“state”: “completed”,
“removestate”: false,
“x”: 490,
“y”: 340,
“wires”: [

]
}
]

2

I cannot test the workflow if you do not put it in a code clock by adding ``` before and after.
But OpenRPA waits for the workflow to complete and it looks to me, like you have both an idle and completed state.

3

Hello, thanks for responding, the code itself is not relevant, it was based on your article: https://discourse.openiap.io/t/starting-an-openrpa-robot-with-openflow-and-node- red/1200/4
The idea is to apply it in reverse, that is, an RPA robot, call a flow, this flow will remain idle until the form is filled in, and only after that, it will be completed.
That’s why the flow has two states. I figured the wait option would work.
Please disregard my English.

4

That will/should work. Openrpa will wait til it completes.
But if you want to involve humans i would recommend you use workitems instead, so you dont loose state in case something restarts.

6

Thanks!
I will study your proposal for the situation. In any case, apparently invokeopenflow only waits until the first update, that is, if I immediately return completed or failed, it proceeds, but if it returns idle, it waits forever even if the item is completed a few seconds later.
Important:
This applies to calling the workflow through rpa, using InvokeOpenFlow, through Assign within nodered, it really works.

7

hmm, to be honest, i have not tested that scenario, so not sure if that would work.
Invoke Openflow was meant to used, to use NodeRED as an API, not to trigger human workflows. But at the top of my head, I would expect it to work.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.