Hi Joost,

I am not sure if I understand. Service Actions are not running as fire-and-forget, you call them and your flow continues when the service action completes and on completion the output parameters of the service action are available.

Are you confusing Service Action here with Client Action?

Regards,

Daniel

Hi Daniël,

I might be confusing them. From what I understand is dat service actions are essentially 'internal' web services. As a web service call runs in it's own thread. I was wondering how I be absolutely 100% sure that the webservice is ready running it's course. So, I thought I need this option. 

I've seen similar options on other platforms where I can choose to run a flow on the client of let the server process it ( because of speed advantages ( no round trips ). However, I might want to wait for the server to finish before continuing myself. Hence, the option 'wait for completion'.

Regards,

Joost

As a developer in terms of how to treat, a service action call is no different from a server action call, except for the fact that it is a distributed transaction. When you call the service action, OutSystems will wait in the current flow, execute the service action on another thread, and resuming the calling flow when the service action is finished, returning the output parameters. If the service action runs into an exception, your calling flow can handle the exception.

There is no option to wait or not to wait for the service action to finish in the platform, you will always wait.

https://success.outsystems.com/Documentation/11/Developing_an_Application/Reuse_and_Refactor/Use_Services_to_Expose_Functionality