Customer Engagement & Dynamics CRM Forum

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

Stop Workflow step makes Dynamics 365 behave differently on real-time workflow compared to background workflow.  While the workflow design is exactly the same in both scenarios, real-time workflows rolls back the transaction, if workflow is stopped with status Canceled.  This is due to the fact that real-time workflows behaves same as a post-operation plugin which if failed rolls back the complete transaction.

Since the background workflow runs outside of the main transaction, it executes each step independently and when workflow is stopped with Canceled status, complete transaction is not rolled back.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

Stop Workflow step makes Dynamics 365 behave differently on real-time workflow compared to background workflow.  While the workflow design is exactly the same in both scenarios, real-time workflows rolls back the transaction, if workflow is stopped with status Canceled.  This is due to the fact that real-time workflows behaves same as a post-operation plugin which if failed rolls back the complete transaction.

Since the background workflow runs outside of the main transaction, it executes each step independently and when workflow is stopped with Canceled status, complete transaction is not rolled back.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

Stop Workflow step makes Dynamics 365 behave differently on real-time workflow compared to background workflow.  While the workflow design is exactly the same in both scenarios, real-time workflows rolls back the transaction, if workflow is stopped with status Canceled.  This is due to the fact that real-time workflows behaves same as a post-operation plugin which if failed rolls back the complete transaction.

Since the background workflow runs outside of the main transaction, it executes each step independently and when workflow is stopped with Canceled status, complete transaction is not rolled back.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

Stop Workflow step makes Dynamics 365 behave differently on real-time workflow compared to background workflow.  While the workflow design is exactly the same in both scenarios, real-time workflows rolls back the transaction, if workflow is stopped with status Canceled.  This is due to the fact that real-time workflows behaves same as a post-operation plugin which if failed rolls back the complete transaction.

Since the background workflow runs outside of the main transaction, it executes each step independently and when workflow is stopped with Canceled status, complete transaction is not rolled back.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

Stop Workflow step makes Dynamics 365 behave differently on real-time workflow compared to background workflow.  While the workflow design is exactly the same in both scenarios, real-time workflows rolls back the transaction, if workflow is stopped with status Canceled.  This is due to the fact that real-time workflows behaves same as a post-operation plugin which if failed rolls back the complete transaction.

Since the background workflow runs outside of the main transaction, it executes each step independently and when workflow is stopped with Canceled status, complete transaction is not rolled back.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

Stop Workflow step makes Dynamics 365 behave differently on real-time workflow compared to background workflow.  While the workflow design is exactly the same in both scenarios, real-time workflows rolls back the transaction, if workflow is stopped with status Canceled.  This is due to the fact that real-time workflows behaves same as a post-operation plugin which if failed rolls back the complete transaction.

Since the background workflow runs outside of the main transaction, it executes each step independently and when workflow is stopped with Canceled status, complete transaction is not rolled back.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.

I have a question about the use of 'Stop Workflow' with status of Success. Can anyone explain (with evidence) why it should be used at the end of a workflow? I cannot find any blog posts, or documentation that explains why so many people are being told to put it at the end of every workflow. So far, everyone I have asked just shrugs and says "I was told to do that" and I feel it is not a best practice.

I can (sort of) understand using it in the middle of a workflow, for example if the person is not a programmer and cannot understand IF logic more than 1 level deep and therefore they are taught to use it to prevent unexpected things to happen. But I cannot understand why people are being trained to put it at the end of every workflow.