This seems to happen sometimes when a connected channel is cloned or migrated. I don't know the precise circumstances that trigger this behavior, but we've seen it from time to time. I would classify this as a bug, but no one has been bothered enough by it to try to fix it.