Latest Contributions by BrentBrock

Thank you!👍 ... View more

The current model I'm working on is purely raster so no joins of any kind, but I've had this issue in every model I've built (well over a hundred by now) since migrating to ArcGIS Pro several years ago.  I opened a support case in June and the issue was assigned #BUG-000150197 but I've seen no indication on progress. I can also confirm that the problem with setting 'ready-to-run' state works both ways as making significant changes to process tools does not always reset the state.  Yesterday I added a tool to the process chain but when I executed the model, it ignored the major modification I made and only processed the last couple steps in the model well downstream of where modifications were made. Clearly there are major issues with the way tool states are being managed in Pro.  This has been a major headache for me as I'm working on a model covering most of North America at 30m resolution.  Even on my beast of a workstation, unnecessarily re-running tools adds hours and often days waiting for results.  The problem is compounded by the fact that some tools like Raster Calculator ignore cancel requests so if a model incorrectly resumes processing on one of these tools, I'm left with the equally bad choices of waiting an hour for the tool to run before the model finally cancels, or killing the whole ArcGIS process in Task Manager. Is there a way to upvote bugs like we can for feature requests? ... View more

Thanks for the update!  Unfortunately, I'm already on ArcGIS Pro 2.9.3 and still having the issue.  Hopefully you will have better luck. ... View more

Were you able to get any answers from tech support on this?  I've been battling this issue since transitioning to ArcGIS Pro 3 years ago.  It seems the 'has-been-run' state is being cleared for processes for no apparent reason and in seemingly random fashion.  This can add hours of unnecessary reprocessing.  Just to be clear, the process states are being changed from 'Has-been-run' to 'Ready-to-run' so it isn't a matter of Pro thinking something needs fixed as it is perfectly happy and more willing to re-run the process as it is than it should be. My work arounds have been to 1) turn off intermediate data for outputs which forces me to manually manage temporary outputs and 2) do as the OP does and add data from previous outputs which breaks the model chain. I've been using modelbuilder since the first release of ArcGIS and didn't have this problem before switching to Pro, so it does seem to be a new bug.  I'm surprised there hasn't been more chatter about this. ... View more

I just posted a potential work around for this if you are on Windows 10 (http://geonet.esri.com/thread/117985). It worked for me anyway. ... View more

Add me to the users frustrated with this error. I've been plagued by it ever since upgrading to 10.1. I'm seeing it with pretty much any of the analysis tools (clip, erase, dissolve...).  All inputs are shapefiles so I'm not seeing the same geodatabase issues as others. But it seems to have something to do with the way layers in the TOC are passed to tools. If you try to drag a layer from the TOC into the tool and it doesn't work, then you know you will get the error. But browsing to the shapefile on the file system instead of trying to input a TOC layer works. The other thing that works is to close and reopen the map doc, after which the tools work again for a little while and then stops again.  Both work arounds are frustrating but at least browsing directly to the sources saves time over constantly restarting the mdx. ... View more

This doesn't work? if arcpy.Exists(your_output):     arcpy.Delete_management(your_output) Nope.  That was the first thing I tried.  I also tried the following to try to get at this without going through arcpy: import os if os.path.exists(your_output):     os.remove(your_output) The problem is that the error is thrown before the script even executes so there is nothing I can add to the script to fix it. Seems to be a validation issue.  I'm going to try deleting the tool GUI and starting from scratch. Brent ... View more

This "feature" also creates fits with Microsoft Activesync. Windows 7 clients on a domain sync user home folders to the domain user share by default. This creates problems if a user wishes to keep both a desktop and mobile computer synced with their network user share and the mobile computer is creating and writing to the default.gdb while not connected. ... View more