Bug Report on Simulink "Unbuffer Block" in R2017a

I found when using the Unbuffer Block in Simulink that a third clock domain was being created in the tool. There should be one domain on the input and one on the ouput, but a third clock domain was being created.

[Suze Zhang]

Hi Lloyd,

By a third clock domain, do you mean the types of sample time that can be viewed from the Sample Time Legend window? And about the third one that you observe with the Unbuffer Block, does it happen to be Hybrid?