Fixed Issue: Apex CPU Limit Exceeded When Saving Multiple Mapping Records #
There was an issue where saving multiple mapping records, such as reference fields, in the mapping tool would result in an “APEX CPU time limit exceeded” error. This issue has now been resolved.
Fixed Issue Did Not Get Field Map on the Mapping tool #
We encountered an issue when creating message types with the same name and sObject type but at different levels. This caused the mapping display to not show the child-level fields for one of them. This issue has now been fixed.
Resolving DML Row Limit Errors in MessageDeletionBatch Apex #
Users set the DoMaintenance scheduler to delete messages. There is an issue with the MessageDeletionBatch batch Apex, which raises the error ‘Too many DML rows: 10001’ when deleting parent and child messages in batches of 200. If the 200 records are all root messages, it queries their child messages again, potentially exceeding the DML row limit of 10,000 records. This issue has been fixed by preventing the unnecessary query for child messages.
