Why Timer Start Event only starts sometimes?

Camunda 7 Topics Discussion & Questions
1

Hi

I have a strange behavior with a workflow that needs to be started daily at 7:10 a.m. This is the start event definition:

 <bpmn:process id="ParentWorkflow" name="Parent Workflow" isExecutable="true">
   <bpmn:startEvent id="StartEvent_1jdyt18">
    <bpmn:outgoing>SequenceFlow_0pk2gn6</bpmn:outgoing>
    <bpmn:timerEventDefinition>
      <bpmn:timeCycle xsi:type="bpmn:tFormalExpression">0 10 7 ? * *</bpmn:timeCycle>
    </bpmn:timerEventDefinition>
  </bpmn:startEvent>
</bpmn:process>

Camunda is running on two environments (currently 7.6 inside Tomcat as an Windows service). The deployments are identical.

On the first environment the workflow is sometimes starting and sometime it isn’t. I also made the experience that the workflow was started once at 15 p.m. instead of 7 a.m. (I think it was somehow rescheduled after restarting the Windows service).

On the second environment the workflow isn’t auto started at all. But in the past there was a similar workflow running on this environment which did start:

<bpmn:timeCycle xsi:type=“bpmn:tFormalExpression”>0 10 7 ? * MON-FRI</bpmn:timeCycle>

I can start it manually using the Task-List in the Camunda Cockpit, but there is another timer issue here: The workflow contains a boundary event that is ignored.

<bpmn:boundaryEvent id="BoundaryEvent_04isz23" cancelActivity="false" attachedToRef="Task_1f5oc9j">
   <bpmn:outgoing>SequenceFlow_0nu4sqw</bpmn:outgoing>
   <bpmn:timerEventDefinition>
     <bpmn:timeDuration xsi:type="bpmn:tFormalExpression">PT1M</bpmn:timeDuration>
   </bpmn:timerEventDe>finition>
 </bpmn:boundaryEvent>

Can somebody imagine what the problem is? Did I miss to configure something that will be necessary for the timers to work reliable?

2

Hello,

Could you please upload you bpmn file.

Best regards,
Yana