...

5. Batch Record was closed successfully

...

CONCLUSION, RECOMMENDATION AND

...

WORKAROUND

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)

Recommendation: Do not deploy the optimization on June R1 release since it’s not fully tested. 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 2 work aroundthe 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)