Single document errors stop tracking of combine

[clementbiron]

Currently, when one single document fails during a combine, the whole tracking process is stopped, even if all other documents could still be tracked successfully.

That puts on the critical path that all documents are properly tracked in order to record any changes, and in the case of large combine, the probability that one of the documents is on error is higher.

The first idea that comes to mind is that all documents in a combine are tracked and monitored independently, so that if one of them is unavailable, the others can still be monitored. The consolidated version would be a step that would be applied later, but it would be necessary to fully understand the implications that this could have. For example, what do we do with the commit history?

[MattiSG]

Thank you for documenting @clementbiron!
Another big difficulty from my perspective regards what to do with the version when some source documents are missing: we don't want to record a version with no content for these parts, as it will trigger change notifications that are inaccurate. The amount of noise could become significant, with flashing parts in the version while no content actually changes.