ArcGIS Pro 2.9 (UN v5): Group Feature Template fails only when EFV and couplings are included.

[Egardner25]

I am working with a Natural Gas Utility Network (version 5) in ArcGIS Pro 2.9 and am experiencing repeated failures when using a group feature template to create a gas service assembly.

The group template includes the following features:

Service Pipe (line)
Riser (set to be added
Tapping Tee
2 Couplings
Excess Flow Valve (EFV)

Builders (Template Construction):

Riser: Point at end of line
Tapping Tee: Point at beginning of line
Coupling #1: Point at beginning of line (Distance along = 2 ft)
Coupling #2: Point at end of line (Distance along = 1 ft)
Excess Flow Valve (EFV): Point at beginning of line (Distance along = 3 ft)

The workflow is:

Start the group template
Draw the service pipe
Fill out all required attributes
Click Finish

At that point, the edit fails and all features are rolled back.

Exact Error Message
Failed to create service line (In Service Plastic) – EFV and 2 Couplings
Error: Unable to complete operation.
Operation rolled back.
Operation rolled back.
Operation rolled back.

I tested a similar group feature template that is identical in setup except that it does not include the two couplings or the excess flow valve. This template completes successfully with no errors. The failure only occurs when the EFV and two couplings are included. 

[RobertKrisher]

Do you have any constraints configured on the junction or device layer that could be causing the failure? Can you successfully draw the couplings and EFV outside of a group template?

[Egardner25]

After reviewing the attribute rules, I don't see any constraints on either the EFV or the couplings beyond mandatory field validation. The only constraints present on PipelineDevice and PipelineJunction enforce required fields based on subtype and lifecycle or in-service criteria. I am able to successfully create both the EFV and couplings outside of a group template. 

[RobertKrisher]

Well, that rules out the obvious problems. If you haven't already, I suggest logging a case with support.

Does it only fail when you include all three features? Or can you narrow it down to just one of those features in the template?