topic Re: ModelBuilder resets tools to 'ready-to-run' state in ArcGIS Pro Questions

ModelBuilder resets tools to 'ready-to-run' state

ChrisD — Mon, 27 Dec 2021 15:27:24 GMT

Hello!

When working with ModelBuilder, tools that I have already run and are in the 'has-been-run' state are very often reset to 'ready-to-run' when I add data to the model or make other changes to the workflow that are not upstream of the change and thus should not have any affect on the reset model elements. It really turns models into a mess because rather than re-running every time a tool resets, I end up adding the data from the previously run tool into the model so I'm not constantly re-running my workflows when this resetting happens. Any help in remedying this would be much appreciated.

Thanks!

Chris

Re: ModelBuilder resets tools to 'ready-to-run' state

DanPatterson — Mon, 27 Dec 2021 21:23:14 GMT

From Validate a model—ArcGIS Pro | Documentation

Ready to run
A process is ready to run when the tool has all required parameters filled in. All model elements in the process have color. If you validate a model and a process changes to not ready to run (elements are gray), it means that one or more tool parameters or input variables are invalid.

Perhaps during the additions you are making to the model, something downstream is deemed invalid.

The help topic also suggests that validation need only be done when you are ready to run the model and not at each step of the building process

Re: ModelBuilder resets tools to 'ready-to-run' state

ChrisD — Mon, 27 Dec 2021 21:34:56 GMT

Thanks Dan, but unfortunately this doesn't solve my issue. I have experienced this behavior with ModelBuilder throughout all the Pro releases over several years, but never with Desktop. I've been using ModelBuilder extensively for a long time, so hopefully I know what I'm doing 🙂 This issue seems like a persistent bug. Maybe someone else can solve the mystery. Thanks for the response.

Re: ModelBuilder resets tools to 'ready-to-run' state

DanPatterson — Mon, 27 Dec 2021 21:43:07 GMT

I would suggest that you open a case with Tech Support since they have the capabilities to see if they can replicate your workflow with your combination of tools and compare differences between Desktop and Pro as the model is built stepwise.. It may be something that Pro "thinks" needs to be fixed (when it doesn't) making your previous steps gray. Graying out of ovals can lead to similar changes in hair color if the root cause isn't addressed. 😉

Re: ModelBuilder resets tools to 'ready-to-run' state

BrentBrock — Fri, 03 Jun 2022 14:41:41 GMT

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.

Re: ModelBuilder resets tools to 'ready-to-run' state

ChrisD — Tue, 07 Jun 2022 15:23:11 GMT

ESRI tech support made the following suggestion, which I haven't been able to implement as I'm waiting on a license server upgrade.

Issue:

Elements' input fields intermittently reset within ModelBuilder in ArcGIS Pro 2.8.2.

Next Steps:

Similar cases suggested that this issue was resolved after updating to ArcGIS Pro 2.9.
However, the user's administrator will need to update to ArcGIS License Manager 2021.1 to manage concurrent use licenses for ArcGIS Pro 2.9.

Upgrading License Manager software from 10.1-10.6 or 2018.0-2021.0 to ArcGIS License Manager 2021.1 | https://desktop.arcgis.com/en/license-manager/latest/license-manager-installation-and-startup.htm#ESRI_SECTION1_7B92A41F71474EB3BC108554C5356F33

Re: ModelBuilder resets tools to 'ready-to-run' state

BrentBrock — Tue, 07 Jun 2022 16:22:17 GMT

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.

Re: ModelBuilder resets tools to 'ready-to-run' state

ChrisD — Tue, 07 Jun 2022 16:59:28 GMT

well, crud

Re: ModelBuilder resets tools to 'ready-to-run' state

robertkalasek — Tue, 29 Nov 2022 13:06:54 GMT

same here with v 3.0.2 aof ArcGIS Pro ... and it is terribly annoying since you either have to wach your model rerunning already existing steps with valid outputs or break the model flow by inserting outputdata from TOC or Catalog ... none of these approaches can be assumed as intentional --- since we are talking about data-flow-graph-based analysis !!!

Re: ModelBuilder resets tools to 'ready-to-run' state

robertkalasek — Tue, 29 Nov 2022 14:31:31 GMT

@BrentBrockand @ChrisD do you use spatial joins, join field (or merge-nodes) in your models ... i think i have identified a problem with field mapping at least in those two (or 3) operations -> i.e. a downstream object shows fields in a dropdown that can't exist anymore at that state of the model but have existed in a step before my spatial join and join field operations (i am not sure about merge !) - i guess the attempt of field-list-matching downstream triggers an upstream-request and the latter is setting back each of the upstream objects

Re: ModelBuilder resets tools to 'ready-to-run' state

ChristopherDeRolph — Tue, 29 Nov 2022 14:51:24 GMT

I use all of the above. I put everything in models and use modelbuilder all the time for table manipulation, vector analysis, raster analysis, etc. If you have a specific model that triggers your issue, definitely reach out to tech support and share it with them. Hasn't resulted in a fix yet, but presumably the more examples and tickets the better. Take care.

Re: ModelBuilder resets tools to 'ready-to-run' state

BrentBrock — Wed, 30 Nov 2022 16:12:47 GMT

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?

Re: ModelBuilder resets tools to 'ready-to-run' state

ShitijMehta — Thu, 15 Dec 2022 15:43:48 GMT

Hello all,
We re investigating right now and based on that we will prioritize it immediately. The tools rerunning unnecessarily is definitely non needed.

Re: ModelBuilder resets tools to 'ready-to-run' state

ChrisD — Thu, 15 Dec 2022 15:45:26 GMT

Fantastic! Thanks!

Re: ModelBuilder resets tools to 'ready-to-run' state

BrentBrock — Thu, 15 Dec 2022 15:54:24 GMT

Thank you!👍

Re: ModelBuilder resets tools to 'ready-to-run' state

ShitijMehta — Fri, 16 Dec 2022 19:43:01 GMT

Hi,
We can repro a case but want to make sure it is exactly what you see. Possible to share just the model or a snapshot of it?

Thanks!

Re: ModelBuilder resets tools to 'ready-to-run' state

ShitijMehta — Fri, 16 Dec 2022 19:45:22 GMT

Hi Chris,
Possible to share the model or a snapshot of it please?
Thanks in advance!

Re: ModelBuilder resets tools to 'ready-to-run' state

ShitijMehta — Fri, 16 Dec 2022 19:47:26 GMT

Hi Brent,
Please can you share your model or a snapshot of it?
Thanks in advance!

Re: ModelBuilder resets tools to 'ready-to-run' state

robertkalasek — Fri, 03 Mar 2023 06:41:28 GMT

unfortunately, the reset to "ready-to-run" error still exists in the current patch - which is pretty annoying if you run models where some nodes take hours to calculate !!!

Re: ModelBuilder resets tools to 'ready-to-run' state

ChrisD — Fri, 03 Mar 2023 14:00:53 GMT

I opened a ticket for the issue – case #03263553. I spent some time on the phone with an analyst trying to reproduce the issue, and wasn’t able to in the few minutes we were in the screensharing session. This is the second time I’ve talked to an analyst and not been able to reproduce the issue during the session. I mean, it happens very frequently for me, but not all the time for every new tool connection. Very frustrating when it doesn't happen during the support call. They always ask me to send in a model with all the underlying data when I do actually have the issue occur, but I haven't taken the time to do it yet. So, feel free to reach out to tech support and reference this case and share models with issues. Such a weird issue that obviously happens a lot for some of us, but presumably not for everyone.