Consider a process in which a discount is applied to a bulk order as a function of customer loyalty and the number of ordered items. Here’s a way to model the process in BPMN:

A precise but unwieldy process model
It’s precise but cluttered and unwieldy. A business rule task is a better alternative to complex chains of gateways:

A much cleaner model using a business rule task
The business rule task (“Determine discount”) leverages a DMN decision table, which is flexible and can be modified easily:

The DMN decision table
So, when you find yourself creating a BPMN process model that includes nested gateways, you may wish to consider a business rule task. It’s clearer, more flexible, and just as precise.