I met the similar situation recently. It looks like the connection problem between publisher and subscriber led to it. When the connection recovered, the subscription came back.