Fix broken mysql master-master replication with GTID

I have a couple of mysql master-master servers running.

Skipping transactions with GTID replication requires injecting empty transactions like so:

STOP SLAVE;
SET GTID_NEXT="0742423dd3-2ef3-1be6-87d9-0ed47aaa28dc:33";
BEGIN; COMMIT;
SET GTID_NEXT="AUTOMATIC";
START SLAVE; 

If I do so on a master-master setup, I end up getting this empty transaction replicated to the second master.

Is there any way to tell mysql that this transaction should not be replicated?

I tried

SET sql_log_bin=0; .... SET sql_log_bin=1;

with no luck.

Thanks!