The process of creating and new version of a template right now has to re-associate all the children pages to the new created template inode, even more nasty is the fact that doesn't even clean the all associations so in database we end up with something like this on the tree table:

child(page) - parent (template)
htmlpage inode 1 - template 1 version 1 - no working no live
htmlpage inode 1 - template 1 version 2 - no working no live
htmlpage inode 1 - template 1 version 3 - no working no live
htmlpage inode 1 - template 1 version 4 - no working no live
htmlpage inode 1 - template 1 version 5 - live working version

So every time a template gets saved it goes grabs all children pages and then creates new entries on the tree table for each of those pages, this didn't use to be an issue before because we maintained the inode of the working version always the same but since we change this policy now we are getting multiple entries for this association in the database

The problem arise when the process of re-associating the pages fails, it ends up leaving the database on an inconsistent state like

child(page) - parent (template)
htmlpage inode 1 - template 1 version 1 - no working no live
htmlpage inode 1 - template 1 version 2 - no working no live
htmlpage inode 1 - template 1 version 3 - no working no live
htmlpage inode 1 - template 1 version 4 - no working no live
htmlpage inode 1 - template 1 version 5 - no working no live

Notice no live or working version of the template got associated with the page.