Certain components in one of our Libraries seem to be stuck in a loop, where it recognized a new updates from the same exact Library I just published and asks me to receive those updates and publish the Library again.
How can this be resolved for those isolated components?
Try to unpublish the library completely or those components specifically and then publish them again.
Tried it at the component level (doing so at the Library level would be too disruptive to our design team) and still didn’t work. I’ll submit a bug ticket for this as well 
Thanks!
It shouldn’t be too disruptive if you make the library inaccessible for just one minute. But yeah submitting a report is definitely necessary.
Hi, I’m having the same issue!
Any input on how you solved it @Chris_Meeks ?
Thanks in advance!
Updating instances of library components works unreliably often. The app claims there’s no updates and then suddenly finds components to update while you are working. I haven’t found a reproducible pattern to it, probably works fine on trivial files.