Currently, Apex Rollup defaults to an async-first approach when performing calculations, but if an org is already at or over their daily AsyncApexJob execution limit, trying to go async will throw an uncatchable System.LimitException.
While still operating in a sync context, that limit should be checkable and the framework can instead calculate synchronously to avoid this uncatchable exception.
Currently, Apex Rollup defaults to an async-first approach when performing calculations, but if an org is already at or over their daily AsyncApexJob execution limit, trying to go async will throw an uncatchable System.LimitException.
While still operating in a sync context, that limit should be checkable and the framework can instead calculate synchronously to avoid this uncatchable exception.