Hey @PersianLord19901!
This seems to be a known bug with the cable component. There may be a possible fix here:
Does this work for you?