Our organization works with a large parcel fabric that contains a lot of data. We have discovered that, currently, once ArcGIS Pro sends a request and the server has it - there is no call back mechanism to be able to stop the request from processing, even if the request is being processed async (and is a job on the server side).
For example: if a user accidentally executes an evaluate rules process on the entire parcel fabric instead of just features that have been modified in this version, and then cancels the process by clicking 'cancel' within ArcGIS Pro, cancelling the operation from a named version does not actually cancel the process on the server. When the user tries to run the process again properly (or, do any sort of edit in the version at all), they cannot and the result is a Serialization lock error. This is because there is no mechanism to stop the process that is running on the server.
When this happens, the user can no longer edit their version and they are prevented from proceeding with their work, at least until the process times out on the server, which can take quite a while.
This ideas post is a reflection of: ENH-000179228: Provide a mechanism to cancel the server-side process when a client-side request, such as Evaluate Rules, is cancelled.
