is a!startProcess_24r3 sync or async

Certified Senior Developer


Hi everyone,

Could someone please let me know whether `a!startProcess_24r3` is synchronous or asynchronous? I am currently using this function in my code, but when I try to upgrade to the new `a!startProcess`, I see a "synchronous" parameter available. So, when I replace `a!startProcess_24r3` with `a!startProcess`, should I set "synchronous" to true or false?. Thanks in advance Slight smile

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    Annoyingly, in doing this update they actually removed functionality that is no longer directly reproducible with the newer version - e.g. you could previously call a Start Process and determine exactly when it would return values to your interface by making use of intentional chaining and chain-breaking. 

    Now instead it either wants to wait the *entire* process duration (regardless of any chaining or attendedness), or the *entire* 30-second timeout, or alternatively, be *entirely* asynchronous (providing zero process details returned, even though the async version currently stalls until chaining is broken in the called process, which i believe is a bug).

    I really wish they'd've given at least an alternate synchronicity option that reproduces the old behavior, because it was honestly quite a bit more flexible for some use cases.

Reply
  • 0
    Certified Lead Developer

    Annoyingly, in doing this update they actually removed functionality that is no longer directly reproducible with the newer version - e.g. you could previously call a Start Process and determine exactly when it would return values to your interface by making use of intentional chaining and chain-breaking. 

    Now instead it either wants to wait the *entire* process duration (regardless of any chaining or attendedness), or the *entire* 30-second timeout, or alternatively, be *entirely* asynchronous (providing zero process details returned, even though the async version currently stalls until chaining is broken in the called process, which i believe is a bug).

    I really wish they'd've given at least an alternate synchronicity option that reproduces the old behavior, because it was honestly quite a bit more flexible for some use cases.

Children
No Data