What’s the difference between the “excludes all” and “does not match” operators?

• Does not match triggers a custom action when the components, labels, or products associated with a launch do not exactly match the ones selected in a command
• Excludes all triggers a custom action when the components, labels, or products associated with a launch exclude all of the ones selected in a command

Let’s say you’d like to build a custom action around three particular labels — Apples, Oranges, and Bananas. 

The does not match command triggers the custom action when the launch is not associated with exactly Apples, Oranges, and Bananas. In other words, the action will not trigger if the launch matches these exact three labels — and no more or fewer. But if there’s any difference between the launch’s labels and the labels you’ve selected, then the action will trigger. 

The excludes all command works differently: it will trigger only if the launch is associated with none with none of the labels you’ve selected. So if the launch is associated with Oranges and Pears, the action will not trigger, as one of the labels you asked to exclude is associated ith the launch. If the launch is associated only with the label Pears, then the action will trigger.