Pipelines taking time to stop


After the last update, when I stop the pipeline. it takes couple of minutes before pipeline completely stops and the status is “Stopping”. During this status pipeline process the data which is unexpected.

Anyone had similar issues? Any work around will be appreciated.

Thank you in advance.

The 4.10 release included some changes to more accurately reflect the status of an execution that has been stopped. Previously, the pipeline would be marked as stopped right away, even though the snaps may have continued to run for a short time after the stop. We will still take a look to see if there are situations where pipelines are not stopping as quickly as possible.