Lemmy will queue announcements to send to other instances with a max retry. Currently, I cannot view the pending queue. The queue is kept entirely in memory too.

If a server is over loaded or the Lemmy backend restarts then this changes are LOST. It’s a terrible experience.

This would explain intermittent issues but not consistent.

I’m looking into the cause of this along with members of the community. I’m also working on a tool to attempt to resolve missed messages.

I know it’s not perfect but the community is working on it. It’s a complex beast that needs some work. We’re working on it.