topic Re: Increased version Post time when updating subnets in ArcGIS Utility Network Questions

Increased version Post time when updating subnets

PierreloupDucroix — Sun, 03 Aug 2025 23:43:31 GMT

Hello,

I would like to discuss the performance of the Post operation in Utility Network when updates have been made in subnetworks.

Explanations :

I am in an 11.3 environment, editing a branch versioned feature service with Utility network. Default is protected and eventing is disabled on default (enabled on versions).

The standard workflow is to edit features in a version and, when needed, to update subnetworks. This will trigger some attribute rules in the version. Then to reconcile and post to default.

When editing features and posting, without updating subnetworks, the Post time is good. Example : move a vertex in a LV cable --> post in ~20 seconds

However, as long as I update the subnetwork, the post time increases greatly, often causing a client-side timeout after 10 minutes.

Same example with only 1 vertex moved, and LV subnet updated --> mode than 10 minutes for a total of 4 changes in the version

After that, the version seems to be locked until the server ends the Post operation. During this time, any operation will cause the error :

SEVERE

4 août 2025, 10:26:27

StopServiceEditing failure (sessionID: {9C555C41-19C2-4E2C-B6BB-B3E9C2B78515}) (User session application lock in progress - operation not allowed) Session Application lock in progress [Session application lock in progress - operation not allowed]

But if I wait enough time, I can get the version access back, then go back to Default and see the edits have been posted.

I don't understand what can cause such an increasing post time.

If anyone has information and solution...

Re: Increased version Post time when updating subnets

RobertKrisher — Mon, 04 Aug 2025 18:58:53 GMT

Are you saying the post itself is taking over 10 minutes? or that the update subnetwork is taking over 10 minutes?

Re: Increased version Post time when updating subnets

PierreloupDucroix — Mon, 04 Aug 2025 20:43:37 GMT

The post time is over 10 minutes.

Update subnetwork can take some time for big ones considering it fires attributes rules, but no more than a couple of minutes.

Re: Increased version Post time when updating subnets

RobertKrisher — Tue, 05 Aug 2025 14:16:33 GMT

Please log a case with support so they can look at your versions, patches, etc. It shouldn't take that long to post so few edits.

Re: Increased version Post time when updating subnets

PierreloupDucroix — Sun, 17 Aug 2025 21:02:48 GMT

After some testing, I discovered that the geodatabase version was causing the problem.

The geodatabase was originally created with ArcGIS Pro 3.3.2. After upgrading to 3.3.4, the time to publish changes became more reasonable (between two seconds and a few minutes maximum, depending on the number of changes).

With the help of Robert Krisher, we identified at least two bugs that could be causing the problem:

https://support.esri.com/en-us/bug/registering-a-class-as-branch-versioned-is-not-creating-bug-000174057

https://support.esri.com/en-us/bug/unable-to-reconcile-or-post-branch-versioned-data-conta-bug-000173394