ATF Test Generator can fail due duplicate update set naming aborted by custom business rulesIssue Automated Test Framework - Test generation can fail with "Processing SNBOQ job failed: Cannot read property "id" from null" or "Processing failed to complete" FactsIn order for the test generation to succeed, the application must be able to create an update set with name "ATF Test Generator - Generated Tests (<scopeName>)". ReleaseN/A - this can be reproduced on any instance with ATF TG and CR in place by adding such business rule.CauseCustom business rules / config may be put in place to prevent duplicate naming of update sets. Due to the fact the test generator inserts update sets with the same name, dependent on the scope, customers may find this action to be aborted by their business rule if test generation for a particular scope has already been ran.ResolutionThere are two options to resolve this. Most importantly, owners of the custom business rule / restrictive config will need to review why it is required. Deactivate the problematic business rule / config.Before running test generation again, any update set having the same name as the generated update set, will need to be removed. Reminder: This is not something that occurs out of box. This has been evidenced in cases where a _custom_ business rule implemented by customers to prevent duplicate naming of update sets is attributed as the cause of the failed test generation.