Merge replication agent is looping after snapshot generation

We have a two database servers that have 3 databases which are deployed with merge replication on SQL Server 2019. It has been working fine for over a year but the replication stopped working on one of the databases even though there were no errors. According to the replication monitor, the databases were synchronizing even though they weren't. 

For the one where the data was not being replicated, we tried to create a new snapshot on the publisher which seemed to work fine and we then kicked off the replication agent which seemed to be doing its thing by generating scripts and getting tables ready for replication. However, it then started looping while trying to apply scripts etc.  There is nothing in the logs that suggest it hit an error but it has done this a few times and we have, so far, been unable to restart replication on this database.

Looking for suggestions as to where to look in terms of status or log files or what might be causing this? A casual google suggested a few things which I don't believe apply to our situation.

Anyone got experience of dealing with a similar situation?