This happend with one of the automatic Cloud Nodes updates in April and yes, correct way to fix it is to copy the executable from oldver folder into cloudnode folder and rename it according to the content of run-cloudnode.sh script.
Hi Gastón,
Please report a bug in our issue tracker and attach test database that you can repeat this in so I can have a look. Paste subject here once done...
From what I've read, using these will store the updated records in memory and then write them to the database in bulk, instead of each record writing to the database in turn. So perhaps there&apo...
