...
The workflow and block are in Redy statusesSafeStop status at the beginning and moved to Stopped status then
Session objects are availabled
DateLastRun is updated or not: it depence on input parameter for stopAfterThisBlocknot updated
Session.vault and Session.vaultGlobal are not moved or not into myVault: it depence on input parameter for stopAfterThisBlock
Stop immediately
The option is proposed for the case when you want to stop processing immediatly and do not wait untill it will be finished. There is a restriction that it can be stopped just in places which call any asyncronius code. It is not a Canvas restriction, it is a Node.js restriction with blocked operations. This description you can get by this link.
It is not recomended option because the bahaivour of integration result may be unpredicted. For example, if you post some data into target application and stopped running before saving in myVault. In this case duplicates can be created next time. Please use this option just in case if integration result are predicted.
Stopping result:
The workflow and block are in SafeStop status at the beginning and moved to Stopped status then
Session objects are availabled
DateLastRun is not updated
Session.vault and Session.vaultGlobal are not moved into myVault
Auto stop
The workflow can be stopped automatically by Canvas block processor, if processor was restarted during processing. One of restarting reason can be a memory exception. If your block was moved to Stopped automatically please contact to CMA support team.
...