This is because Mistral gets out of sync with ST2. At a past job we ran to this frequently in our development environment. In our case we would pause the workflow and they would pause in mistral, and stay in pausing in ST2.
I no longer have access to the script that I wrote for this, but this is what I remember off the top of my head.
You will need the mistral execution ID, which is different from the ST2 execution ID. Look in MongoDB at the action execution collection. You’ll need to find the document for the ST2 execution ID. I think the field is parent_process_id. In that document will be mistral execution ID.
Once you have that you can use the mistral command to resume or cancel the process. You can execute the command “mistral execution-update -S NEWSTATE MISTRALEXECUTIONID”. This will tell mistral to transistion the workflow. When mistral transitions the workflow, it will call home to ST2 and it will reflect the updated state.
Sorry I don’t have more detailed steps.