AnsweredAssumed Answered

Tech Connector: AtomSphere API Execute not returning an error response

Question asked by kat.austria697779 on Jul 13, 2016
Latest reply on Jul 20, 2016 by kat.austria697779

I'm developing a process that needs to dynamically call other processes.

In order to trigger the execution of a process, I'm using an AtomSphere API connector with an Execute operation.

I managed to successfully trigger another process through this, however I did run into an issue - it doesn't seem to be returning error response. To be clear, I'm not looking for the error returned specifically by the process that was triggered. In my case, I had not deployed the process, so I am guessing that's why the process didn't run the first time - but there was no way for me to know that, because the call using AtomSphereAPI returned success.

 

Is it that it's async so by default the response is basically acknowledging that it successfully received the request - so essentially as long as you pass some parameter values? Does it do additional validation? When can we expect an error or a failure response (aside from parameter values not set for processid and atomid) ?

 

 

Thanks in advance.

Outcomes