I know this post is old but it's worth adding context.
The Fusion handles MIDI CLOCK sync well when it's receiving external MIDI CLOCK. I know of no issues with clock RX.
It handles being the MIDI clock master seemingly as well UNTIL the volume of MIDI data exercises a logic bug in the Fusion code that causes a total loss of sync. The Fusion has to be power-cycled to return to normal operation once this happens. I think the sync code runs out of space to insert a clock message and just goes nuts. I imagine the code looks something like this.
if (open_stream_slot)
{
insert_clock(open_stream_slot);
}
else
{
log_error("err: no slot for CLOCK"); // this should never happen
}
It can be triggered by high-density controller data like pitchbend or aftertouch on the Fusion or even by playing a very dense MIDI sequence.
In a multi-device setup, I recommend disabling MIDI CLOCK TX on the Fusion and allowing some other piece of gear (drum machine, etc.) to act as master clock source.
If you're just using the Fusion by itself, disable MIDI CLOCK TX and you'll have no issues.
Here's more info.
viewtopic.php?t=6948&hilit=Clock