What is the recommended approach to handle errors in an Integration Procedure?

What is the recommended approach to handle errors in an Integration Procedure?

• A. Ignore and continue.
• B. Use Fault/Throw error handling with optional logging for troubleshooting.
• C. Only log without returning payloads.
• D. Retry indefinitely.

Answer: (B)

When an Integration Procedure encounters an issue, you should handle it with a structured error path rather than letting things fail silently. The recommended approach is to use Fault/Throw error handling to catch problems and then throw a structured error back to the caller. This creates a consistent, predictable failure path that downstream services or users can detect and respond to, instead of returning partial data or continuing as if nothing went wrong. Optionally, log the error for troubleshooting. Logging gives you diagnostic context to investigate failures without affecting the error payload sent to the caller. This balances visibility with clean error handling. Avoid ignoring errors or retrying indefinitely, as that can hide problems and create long-running or looping processes.

When an Integration Procedure encounters an issue, you should handle it with a structured error path rather than letting things fail silently. The recommended approach is to use Fault/Throw error handling to catch problems and then throw a structured error back to the caller. This creates a consistent, predictable failure path that downstream services or users can detect and respond to, instead of returning partial data or continuing as if nothing went wrong.

Optionally, log the error for troubleshooting. Logging gives you diagnostic context to investigate failures without affecting the error payload sent to the caller. This balances visibility with clean error handling. Avoid ignoring errors or retrying indefinitely, as that can hide problems and create long-running or looping processes.