The synchronous type of proxy workflows preserve the API and the operation contract of the remote workflows.
The schema of all synchronous proxy workflows is the same, but contains different scripting.
The synchronous proxy workflow completes the run after the remote workflow completes and provides output parameters.
The local workflow consumes no server resources while waiting for the results of the remote workflow.
At the end of a successful run the output parameters of the proxy workflow contain a local representation of the remote workflow token. The output parameters can be used directly by other workflows on the local Orchestrator server when they are of simple type, such as, boolean, number, string, and similar.