Reduced Limit for Number of Actions in a Boxcar Request

Immediate Mitigation

To avoid hitting the new 250-action limit, reduce the number of Aura server-side actions enqueued in a single component lifecycle. Review your Lightning components and identify locations where large numbers of $A.enqueueAction() calls are made in rapid succession within the same rendering cycle.
Steps to mitigate immediately:

1. Audit your Lightning components for loops that call $A.enqueueAction() more than 250 times in a single pass.
2. Break large batches of server calls into smaller sequential calls using callback chaining or a queue-based pattern.
3. Consider caching server responses using storable actions (action.setStorable()) to reduce repeated server calls.

Long-Term Remediation

For a permanent fix, refactor your server-side Apex controllers to consolidate multiple small data retrieval calls into fewer, larger calls that return more data per request. For example, if a component makes 300 individual getRecord() calls, consolidate them into a single Apex method that accepts a list of IDs and returns all records at once.