#CPU Timeouts2 utenti parlano di questo argomento

Hi Robin, the timeout is because you are updating every matching Opportunity in one synchronous transaction when the target changes, that will always blow the CPU or DML limits at volume. The fix is to move it async and only touch rows that actually need it. 

1. Do the mass update in Batch Apex (or a chained Queueable), not directly in the trigger or flow. Batch processes the opportunities in chunks of 200 in separate transactions, so each chunk stays under limits and the whole set completes without a timeout. 

2. Filter to a true delta instead of re-updating everything. In the batch query, select only the opportunities that still need the change, for example where the Sales Target lookup is null or different AND region and business unit match. That is your exclude-already-updated idea, but done in SOQL, so no separate custom table to track it. 

3. Better long-term, flip the direction. Rather than the Sales Target pushing its Id onto thousands of Opportunities, resolve it on the Opportunity side: a before-save flow or trigger on Opportunity sets the Sales Target lookup from that record's own region and business unit when it is created or edited. Then the work is spread across individual cheap saves, and a target change only needs a one-time async backfill of existing records. 

Net: async batch fixes the immediate timeout, the SOQL delta keeps re-runs cheap, and maintaining the link on the Opportunity side avoids the giant bulk update going forward. 

if this helps, please mark it as the Best Answer so it helps the next person, thanks 🙂

Hello Laura, 

That CPU time limit error you're getting while updating the Kanban Board in Agile Accelerator is likely due to the managed package running too much Apex behind the scenes when saving the changes. Since it's a managed package, there's not much you can tweak directly in the code, but you can try a few workarounds. Try doing the update in an incognito window or a different browser to avoid any caching issues. Also, see if you can temporarily reduce the number of records or columns on the board — that can ease the processing load. Some users have had better luck by cloning the board and then making edits to the cloned version. If you’ve got any custom automation on Work or Status objects, try disabling it just while you make the update. And since you were successful after a few tries in the sandbox, trying again during off-peak hours might help. If all else fails, ask Salesforce to escalate it to the Agile Accelerator team — they might be able to suggest a fix or workaround.