Skip to main content
June 20, 2025
Question

Integration call design

  • June 20, 2025
  • 7 replies
  • 0 views

Hello All,

Is there any occasion CALL INTEGRATION node will stall and gets stuck for any reason (300s, 400s and 500s HTTP)? I expect it moves on irrespective of the call result. I don't plan on handling exception in the node but examine the result/error after the call. 

Would like some recommendations from the community.

Thanks.

7 replies

stefanhelzle0001
June 20, 2025

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

June 20, 2025

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?

stefanhelzle0001
June 20, 2025

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

June 20, 2025

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

srmm0001
June 22, 2025

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.

June 30, 2025

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.