What is the difference between synchronous and asynchronous Integration Procedure calls?

What is the difference between synchronous and asynchronous Integration Procedure calls?

• A. Synchronous returns a response immediately within the flow; asynchronous calls run in the background and return control while completing later.
• B. Synchronous calls run in the background and complete later; asynchronous returns a response immediately.
• C. Both behave identically with no differences.
• D. Asynchronous calls block the flow until the external call finishes; synchronous calls do not.

Answer: (A)

The key idea is blocking versus non-blocking execution when you call an Integration Procedure. A synchronous call waits for the procedure to finish and returns its results as part of the same flow, so the flow is paused until the IP completes. An asynchronous call starts the work and returns control right away, while the IP continues running in the background and the final result comes later. This distinction matters for user experience: use synchronous when you need the result immediately to drive the next steps in the flow; use asynchronous when the task might take time and you don’t want to hold up the user interface or the rest of the process.

The key idea is blocking versus non-blocking execution when you call an Integration Procedure. A synchronous call waits for the procedure to finish and returns its results as part of the same flow, so the flow is paused until the IP completes. An asynchronous call starts the work and returns control right away, while the IP continues running in the background and the final result comes later. This distinction matters for user experience: use synchronous when you need the result immediately to drive the next steps in the flow; use asynchronous when the task might take time and you don’t want to hold up the user interface or the rest of the process.