...
5. Batch Record was closed successfully
...
CONCLUSION
...
& RECOMMENDATION
...
The CPU time limit is a known error from Affinaquest as they don't have a configuration to adjust the Batch Size. This is still encountered during the test in RommelTest sandbox (Affinaquest version 24)
Completed Testing in SIT: SIT Testing Result
Open Items for Testing: TAP-1200/1222/1219 Issues Unit Testing
Bug in Join utility which blocks accounts being joined
Recommendation:
Do not deploy the optimization on June R1 release as part of May R2 Release since it’s not fully tested in SIT. MS team will revisit all possible options to further optimize related flows and processes.
Workaround:
Users can still use the existing process, whenever they encounter the issue during closing of batch, we have the following options:
Option 1: MS team will run the code via dev console to close the problematic Batch Record using the specific ID of the Batch record;
Option 2: MS Team created a custom “Emergency Close Batch” button that will do the same logic/process mentioned in option 1. This custom button will enforce the system to just use Batch size 1 instead of the default 10
Option 3: Affinaquest to provide configuration settings that can control the Batch Size (This can be considered as enhancement, as per AQ support)and Yeng Sembrano will get more information from Affinaquest about how the batch process works on the background so we can do a Customized
Close Batch button that can be run whenever CPU time limit happens in PROD as an interim fix.