Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

[JoabelBarbieri]

Anything you try to cancel in ArcGIS PRO just gets hanging and spinning and it won't finish. It seems PRO tries to finish the process before cancelling which is a HUGE waste of time and resources. Having to kill the exe, losing all your work is a constant. ESRI must address this issue

Example where I canceled and it's spinning for MORE than 15 MINUTES !!!

[UseItOrLoseIt]

The developers are worried about corrupting data, yet everyone here ends up simply ending the task in Task Manager which I assume would pose the same risk. The first report of this issue is from 5 years ago! I just had to cancel a data export of a single point that hung up. First the export itself hung up for 10 minutes, then canceling it hung up for another 10 before I finally shut it down via Task Manager. I moved from ArcMap to Pro about 2 years ago, and this has been a fairly common problem since then for me. 

[GISAdminSHN]

It might pose the same risk, but notice the subtle shift in accountability....

If we choose to use End Task then the data corruption becomes our fault for not letting the tool or cancel complete! 😄

[BrianSchrock]

This is easily the most infuriating issue I have with Pro. I am testing a model on Pro. All it has to do is calculate ONE field on ONE point. That calculation is literally Field = 242. It was calculating for minutes with no progress. I tried to cancel and it would probably go on for days if I let it. FOR THE LOVE OF ALL THAT IS HOLY, ESRI, where are you on this issue? Why cant the simplest of task ever stop? Why have a stop button at all if you didn't program it to do anything? Is it just there to be a troll button?

[EmmaSchultz1]

Just adding to the thread for this consistent issue. Testing out Pro 3.4.1 and this is still happening for any type of cancellation. The not wanting to corrupt data reason makes sense for geoprocessing, but what about for simple tasks like identify tool? I cancelled an identification and it has been hanging there for 15 minutes. There is no data to corrupt in this case so not sure why it can't cancel. 

[FakeName]

Slight update:

Obviously ESRI has known about this problem (cancelling processes and the GP Framework) for years. According to ESRI's own documentation, this issue was "under consideration" during both the 3.3 and 3.4 "performance improvements". Explanations from ESRI, such as "tool execution" and "responsiveness" have been speeded up so the cancellation process is faster, simply don't address reality.

In the end, unfortunately, nothing has been done. In my opinion, ESRI engineers know what the problem is but have no idea how to address the issue. And executives don't want to spend money trying to figure out a solution.

[Dark]

6 years since this thread was created, imagine ESRI improving their software LOL...