This looks to be a re-occurrence of https://support.esri.com/en-us/bug/the-find-overlaps-tool-in-the-intelligence-toolbox-in-a-bug-00014...
I have a custom geoprocessing tool that uses FindOverlaps and a set of test data with numerous polygons, some of which have overlaps and some do not. The code previously ran successfully in Pro 3.1 and 3.3 on that dataset. However, now i get the same error described in a 2022 thread on the above bug.
ERROR: Find_Overlaps
File "REMOVE\ArcGIS\Pro\Resources\ArcToolbox\Scripts\intel\analysis\FindOverlapsLogic.py", line 241, in process_overlaps
input_seDataFrame.spatial.to_featureclass(temp_fc)
Object: Error in accessing describe
ERROR: Find_Overlaps
File "REMOVE\ArcGIS\Pro\Resources\ArcToolbox\Scripts\intel\analysis\FindOverlapsLogic.py", line 356, in subset_dataframes
overlaps_sdf, extent, fcount = self.process_overlaps(input_seDataFrame)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cannot unpack non-iterable NoneType object
ERROR: Find_Overlaps
File "REMOVE\ArcGIS\Pro\Resources\ArcToolbox\Scripts\intel\analysis\FindOverlapsLogic.py", line 529, in generate_overlaps
overlaps, centroids = self.subset_dataframes(input_seDataFrame=sdf, field_group=None)
^^^^^^^^^^^^^^^^^^^
cannot unpack non-iterable NoneType object
python-BaseException
Additionally, encasing that FindOverlaps function within a try/except doesn't seem to work:
try:
arcpy.intelligence.FindOverlaps(
in_features=in_memory_polygons,
out_intersection=overlaps_output,
out_centroid=overlaps_centroid,
)
except:
self.logger.warning(
f"FindOverlaps failed for {self} with {in_memory_polygons}"
)
return
Furthermore, I have confirmed that the input for in_memory_polygons contains records with both a arcpy.GetCount validation and by viewing the result in debug mode.
Question for you - are you using ArcGIS Pro Intelligence or ArcGIS Pro AllSource? ArcGIS Pro Intelligence was retired and rebuilt into ArcGIS Pro AllSource. I have ArcGIS Pro 3.4 and ArcGIS Pro AllSource 1.3.0 on my laptop. I tested the Find Overlaps GP tool in both (did not use Python) and both GP tools processed correctly with or without overlaps.
It might be worth raising a support case with your local Esri distributor and have them investigate this issue