Hello everyone,
We are using the process engine within an integration layer to orchestrate service calls, and we have the following challenge.
After a release, the data of individual environments is cleaned up and deleted, which results in the inability to properly terminate the current process instances in Zeebe. Now, the question arises whether it is possible to find and stop the processing of the ongoing instances in Zeebe.
Best regards
Florian
Hey there @riebdt! 
There is no possibility to just “stop/pause” process instances in Camunda Platform 8 yet.
You only can cancel all the running instances. This could possibly be automated by fetching all running process instances from the Operate REST API and cancelling them through the Zeebe gRPC API.
Let me know if this answered your question! 
Best,
Thomas
Hi @Hafflgav,
thanks for you’re respond.
That’s what we’ve been using so far.
Unfortunately, we also had the case that in one environment the state of Elastic was not synchronized with Zeebe.
But as far as I understand there is currently no other solution and there are no plans to introduce one?
Best regards
Florian