I think you might have to do something hacky by scheduling it so far into the future it just doesn’t execute.
How are you packaging your deployments? You mentioned Spring, is this a Spring project? I ask, because if it were me, I may try to manage it at the packaging level. If I wanted to disable the cron scheduling for a process app in QA, for example, I may have a QA build profile that removes the timer definition completely during packaging, i.e. removing <bpmn:timerEventDefinition> from the XML entirely,
thank you for your ideas. As of now, I set it to a date in a far future (as is also recommended on stack overflow). I just hoped there would be something similar to the Spring’s syntax in camunda. That would be more expressive. Actually, after a thought: a dash is not expressive at all hence a comment would have to be written anyway. And then, a date in the future is equally good
As for modifying processes during packaging / deployment… This is a no go in my view. For any software.