BUG

Prune Branch History with an empty ‘Prune Before Date’ ignores referenced moments resulting in additional rows being pruned

Last Published: March 17, 2026

Description

Executing the Prune Branch History geoprocessing tool without a value for the ‘Prune Before Date’ parameter can incorrectly prune additional rows in ArcGIS Pro 3.5 and 3.6. When this issue is encountered, features can disappear from versions if the feature was updated or deleted in the Default version. An additional side effect is that reconcile may fail to detect conflicts and/or replicas can fail to detect changes.

Cause

When the Prune Branch History geoprocessing tool is executed without a ‘Prune Before Date’ parameter, the tool should detect the oldest referenced moment and use this moment for the prune operation. Because of this issue, the Prune Branch History tool is ignoring the referenced moments and uses the current moment and incorrectly deletes dependent rows. 

Workaround

Specifying a valid ‘Prune Before Date’ moment will ensure the correct behavior.

Note:
ArcGIS Pro 3.7 and upcoming ArcGIS Pro 3.6.x and ArcGIS Pro 3.5.x releases will correctly use the oldest referenced moment for the operation.

Article ID: 000040852

Get support with AI

Resolve your issue quickly with the Esri Support AI Chatbot.

Start chatting now

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Start chatting now

Go to download options