2. Bug Fixed

Fixed: Reprocessing API Message Created in SYNC Mode Shows Null Pointer Error

We fixed an issue where reprocessing an API message created using invokeCalloutV3 in SYNC mode could update the message comment with the following error:

API Message, 205, Message: Attempt to de-reference a null object

This happened during message reprocessing when the outbound interface used a REST Adapter and a Fault Interface/response handling flow. The original API response was returned correctly, but after reprocessing the same IMessage, the comment could be overwritten with the null object error instead of keeping the correct backend response message. The issue occurred because the reprocess flow could run without the original CallOutControl input parameters, and in some cases, the configured Fault Interface relationship was not loaded when the REST response was processed again. The reprocessing logic has been improved so that V3 outbound REST messages created in SYNC mode can be reprocessed consistently. Missing callout control parameters are now handled safely, and the Response/Fault Interface is loaded correctly during inbound response processing. After the fix, reprocessing preserves the correct backend response handling and no longer fails with the null-object error.