Some aggregation properties will only be updated when certain conditions are met e.g. total number of related x to y could only update for any entity change in a related x. Some aggregation properties are also usually static after an initial period of updating and will likely never be updated again.

For these recalculating every 15 minutes will result in lots of unnecessary work. What if instead these aggregation properties could be triggered by an update to a downstream related entity either before or after so only have an update when necessary. So when an entity of x is updated the aggregation update is triggered for the before y and after y.

The reduction in work and processing could even mean this type of aggregation could avoid the limit for aggregation properties.

An automation could even be used to trigger the relevant updates as this can already handle the any change to the relation logic and would impose rate limits making sure the amount of updates stays sensible