I deploy the process to orchestrator and then run the process using orchestrator’s start jobs api.
Then, I wanted to receive an output argument returned as a result of process execution, but there was a problem that Null was returned.
This was because start.jobs api did not wait until the end of the process, so null was returned, and in order to get the output argument, I send get/odata/jobs(id) api after the process.
But I didn’t know how long it would take until the process was over, so I wanted to know when to send get api.