Unique key violation error was seen when trying to save or submit a subproject. Issue A unique key violation error was seen when trying to save or submit a subproject. CauseThere was a custom business rule in place which is failing and creating a record with the prefix TASK. So once the user clicks save it seems like that business was creating a TASK record with the sys_id for the subproject. This creates a unique key violation error as that sys_id is already taken by the TASK record. ResolutionDisabling the business rule and creating an example subproject worked as expected. To find the right business rule "debug business rule detail" was run.