Lag using Call Integration Smart Service

RE: Lag using Call Integration Smart Service

jjzemmouri — Wed, 26 Jan 2022 08:37:21 GMT

Thanks Stefan,
It brings a new light on what should be taken into account while we're designing a process model.

RE: Lag using Call Integration Smart Service

jjzemmouri — Wed, 26 Jan 2022 08:34:33 GMT

Thanks Peter,
As you suggest, I will gather precisely the users' expectations, and will create a new post.

RE: Lag using Call Integration Smart Service

Peter Lewis — Thu, 20 Jan 2022 20:15:22 GMT

It would be useful for us to know how this is impacting you. Is there a user waiting on the results of this before going to the next form? Is there something in your process that is timing out because it's waiting too long? Also in general I'd recommend creating a new post - it's possible that the original poster isn't even in this community any more and it's easier to stay organized with a new post.

RE: Lag using Call Integration Smart Service

Stefan Helzle — Thu, 20 Jan 2022 16:45:39 GMT

Node execution time in a process is controlled by the execution engine and does typically take way longer that an integration call or a call to the database.

Appian is made to run a million processes simultaneously, not to run a single node in minimal time.

RE: Lag using Call Integration Smart Service

jjzemmouri — Thu, 20 Jan 2022 16:21:04 GMT

Hi,
We're facing the same problem you described.
Have you collected more information about that behaviour ?
Did you find a workaround ?

RE: Lag using Call Integration Smart Service

viveku3486 — Tue, 08 May 2018 14:46:51 GMT

Hello Brazil,

Integration makes a call on the url you have added inside it including any json parameters as body. Its totally depends on the overall time the url is taking to complete your request. To check further you can use fiddler or postman and make the same call from them to see how much time its taking to execute.