nopes. it only happened because you changed the parent of a component with another one.
in my experience that change tends to get screwed.
maybe there’s a way to fix it in cpp or bp but i don’t know of it.
maybe by making the component reparent correctly on the bp constructor (make sure you call the parent constructor (right click on the function name node > add call to parent)
to reparent use this How to change parent class of blueprint asset? - #3 by IphStich
blueprint change parent at DuckDuckGo