In API driven workflows, users must poll the Aria Config API (RaaS) for the status of the job to know when it is complete. Long running orchestrations executed via the API are timing out, or marking the job as complete early. This causes the job status to show complete with no returns and no errors in the job status info. The same info will also appear in the UI.
Eventually, when the orchestration completes, the actual job results will be updated. However, it is not possible to track the actual job status at this time. Therefore, the best course of action for now is to continue to poll RaaS for the job results up to a max timeout beyond when the job might be expected to complete. We also recommend using a method such as exponential backoff when polling the API to avoid overloading RaaS with status update requests.