Hi, We have a process model that is started on a start timer node that is s

Gary, not sure that I understand what you mean by 'the current active one'. Is one process instance still active because there was data in the table? If you have removed the start timer, no future process instances should be automatically kicked off.

@ashvink - OK I see what you mean. Yes, there is one active because it found data and the task that was spawned as a result of it has not been completed yet. So, if there was one that was not active, is there a way to stop the timer node other than removing the timer from the start node and re-publishing?

Gary, if you want to stop an active instance, you could always monitor the process instance and manually start a terminate end event. That will cause all active flows to terminate, which would make the active instance end. If no terminate end events exist in your model, you can edit that instance, add a terminate event, and then start that event through the Monitor functionality.

If you are trying to ensure that the process does not start in the future, your approach of removing the timer and re-publishing is a correct one. Whenever you want to resume the timer, remember that you can revert the process model to a previous version so you eliminate the risk of re-entering the code incorrectly.

Let me know if I'm still not understanding your question fully.

You could put an XOR node right after the start event and test the value of a constant to go straight to an end event or continue. Then toggle the value of the constant to control what the process does.