3. 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.

Fixed: Google Drive Adapter Start Consumer Button Disabled

Fixed an issue where the Start Consumer button on the Google Drive adapter could remain disabled even when the Google Drive adapter had a successful Ping Status. This issue has been resolved, and users can now start and stop the Google Drive consumer successfully.

Migrated Bulk Delete message processing to Salesforce Bulk API 2.0

In previous versions, bulk message deletion used the legacy Salesforce Bulk API behavior. This could cause failures when users delete many messages from Message Monitoring, especially during Delete All processing. The delete flow now uses Salesforce Bulk API 2.0 REST ingest processing. SKYVVA creates a JSON bulk job, uploads the delete records as CSV data, and closes the job with UploadComplete so Salesforce can process the deletion asynchronously. This improves compatibility with the current Salesforce Bulk API behavior and supports bulk delete processing through the newer REST-based Bulk API 2.0 flow.

Fixed an issue where IData was not displayed on the IMessage record for some V2 interface messages

The issue happened when the IMessage Data__c field was empty and the message payload was stored as a related file instead. For large message payloads, SKYVVA stores the data in Attachment or ContentVersion because Data__c has a size limit. In this case, the system tried to read the data from ContentVersion, but some V2 messages had the data stored in Attachment. Because the fallback to Attachment was missing, the IData section appeared empty. The logic has been updated to first check ContentVersion and then fall back to the related Attachment when no data is found. This ensures the IData is shown correctly on IMessage records created from V2 interfaces.