It is common for people to open up completed workflows to view the final information collected (documentation in the End Event). I noticed that when loading this last page the cancel/notify was being called in the Workflow Processor. This happens because of changes in the front end that will call a reset_token whenever a specific page is requested. We just need to check and make sure that if the reset_token is called and the workflow is already complete, and the request is for the end event, that we don't call the cancel notify.
It is common for people to open up completed workflows to view the final information collected (documentation in the End Event). I noticed that when loading this last page the cancel/notify was being called in the Workflow Processor. This happens because of changes in the front end that will call a reset_token whenever a specific page is requested. We just need to check and make sure that if the reset_token is called and the workflow is already complete, and the request is for the end event, that we don't call the cancel notify.