timecycle defintion

[gwaptiva]

I have a process that needs to start each day at 5am. So I have a process that defines

<startEvent id="myprocessid">
    <timerEventDefinition>
        <timeCycle>0 0 5 * * ?</timeCycle>
    </timerEventDefinition>
</startEvent>
‍‍‍‍‍‍‍

Is this the correct definition?

In case you're wondering, when I deploy this definition into our application-with-embedded-Activiti-5.7 the first run appears in the act_ru_job table for tomorrow morning 5am, but it doesn't.

Just before I start pulling what's left of my hair out trying to find the cause in our source somewhere, can someone please confirm that above timeCycle definition is the one I need to start every day at 5am?

Thanks

[Edit: Additional info: instead of starting every day at 5am, it starts a few (3-4) hours apart, something like 9ish, 12ish and 16ish. ]

[gwaptiva]

Secondary question: is it intentional that scheduled jobs are not undeployed when the process defniition is undeployed, but when I re-deploy the definition?

Put a breakpoint at DeleteJobsCmd#execute() and it only gets called when deploying a process definition

[gwaptiva]

Hi

I needed an upgrade to 5.9 to be able to scale my flows (using the asynchronous continuations) and discovered that the issue with "undeploy does not delete jobs" has been resolved.

Never found that on any patch list ( must be my :shock: ), but thanks anyway!