Hi Robert,
As suggested, we dropped the topology and removed the laterals from the subnetwork line definition. After enabling the topology and restarting the service, that part seems to have worked well. However, now we are receiving an error that appears to be related to attribute rules and an L### prefix in front of the feature class name. This seems odd as the only change we made we the subnetworkline definition.

Let me know if you have ideas or if this warrants a separate post. I'm certain I've seen this before but can't find the resolution again.
Many thanks,
Mike