I have found the issue, but it will be a good few days before it will be released by Apple on the app store, so here is the issue and a workaround.

For all revision sets that don't have scheduling attached to them (most of the sets, like radius maps, postcodes, categories, some bike lists, some custom lists don't have schedules so all are affected). The issue is the scheduler leaves an open transaction on the database, what its meant to do is open a transaction, do a bunch of work, then either commit or rollback the transaction, what the end result is, is that everything that happens after that point does not get written to the device but is left in memory until the app is closed then you lose all your work that happened since the revision set was revised.

The workaround is that in the maintenance screen near the bottom of the screen is a "Commit transaction" button press this, it will commit any open transactions and the app should continue to work, unfortunatly this has to be done after every revision until the new build is released by Apple.

For once this is not Apple's issue but an oversight on my part when coding the scheduling function recently, so please accept my appology for this issue.

 ATB

Alex