itadakimasu, 1 year ago

I fixed this on some communities by unsubscribe and subscribing again (after the instances updated to 0.18.X)