...
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)
Users can still use the existing process, whenever they encounter the issue during closing of batch, we have 2 work around:
...
MS team will run the code via dev console to close the problematic Batch Record using the specific ID of the Batch record;
...
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 as part of May R2 Release since it’s not fully tested in SIT. MS team 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.