Integration call design

RE: Integration call design

ganesh.raju — Mon, 30 Jun 2025 17:44:40 GMT

Hi maheshp460,

No, the Call Integration node does not stall forever on 300s, 400s, or 500s unless there’s a network or timeout issue/misconfiguration in object.Check the response downstream to just make sure your timeout is reasonable and you're not relying on exception flows for status code logic.

RE: Integration call design

SRINIVAS M — Sun, 22 Jun 2025 04:26:56 GMT

Hi,

I think In Appian, the Call Integration smart service does not stall on HTTP 300s/400s/500s. It completes execution with success: false, allowing the process to continue. Errors like timeouts or unreachable URLs are captured in the integrationError output, which you can handle downstream as needed.

RE: Integration call design

Stefan Helzle — Fri, 20 Jun 2025 18:38:03 GMT

That's good. Then it is really up to you to decide whether your process may proceed.

RE: Integration call design

maheshp932706 — Fri, 20 Jun 2025 17:43:45 GMT

Fake URL does not stop the node. It still moves on and with success = false; Integration error will have error message.

RE: Integration call design

Stefan Helzle — Fri, 20 Jun 2025 15:24:40 GMT

I did not run into such a situation recently. Use a fake URL and try it.

RE: Integration call design

maheshp932706 — Fri, 20 Jun 2025 15:08:10 GMT

My understanding is that network error will return success as false and status code as null. Integration Error object will have the error message. Yeah?

RE: Integration call design

Stefan Helzle — Fri, 20 Jun 2025 14:24:41 GMT

I have seen these nodes failing in case the other side was not available, meaning a network timeout.