Un-retraction after M600 manual filament change, causing a blob on the prime tower

[acoustic light]

After setting "Retraction when switching material" to 0mm on a Centauri Carbon 1 (without CANVAS) to remove a 2mm unretraction after M600 that generated a big blob, I found that I'm still getting un-retractions to compensate for the standard travel retraction that happened before the M600.

The Centauri Carbon 1 firmware performs a 120mm extrusion upon print resume (after manually changing the filament), but it seems that OrcaSlicer is still tracking a "pending unretraction" and performs it after the M600, even when the nozzle is already full.

I'm not sure if I'm doing something wrong, the Centauri Carbon default profile could be improved, or this is a limitation in OrcaSlicer.

Any ideas?

[sturdy finch]

While some users on the original Centauri Carbon have had success with M600, it is reported as unreliable. CC2 doesn't even support it at all according to elegoo (Reddit) better way is: pause on the printerscreen
retract old filament and remove it,
insert new filament,
extract until new color is extruded,
resume.