We have discovered that a number of projects from September (identified so far) have had processed survey features 'reprocessed' unknowingly, and against our wishes, which 'reverted' edited features back reflect the original survey points.
I can't be sure what version of TBC was used at the time and we are struggling to recreate the scenario with V5.32 (even deliberately) to identify the cause and move to prevent it.
Previously we addressed this with the 'Project Setting>Feature Code Processing' setting 'Allow editing of processed feature codes and reprocess feature codes during Compute Project', and were making an effort to ensure this was unchecked in all templates. A number of the problem projects have this setting checked, but now the features won't reprocess when we deliberately edit features and Compute Project manually (as opposed to auto during export and/or save).
Has anyone else experienced similar issues, or is there a known issue/bug?
We don't want features reprocessing, and are trying to ensure we are configuring TBC and using methods to prevent this, but struggling to control when this does/doesn't occur automatically.