Camunda engine problem with timer cycles. One extra execution while using repetitive timers

So in my project we’re using an embedded camunda engine in a spring boot application and it’s external task feature. The way we build the BPMN model instance is using the Java API:

Bpmn.createExecutableProcess()
        .id(jobDefinitionKey)
        .name(connectorDiscriminator.getName())
        .startEvent()
        .timerWithCycle(trigger.getValue())
        .serviceTask(connectorDiscriminator.getTopic())
        .camundaExternalTask(connectorDiscriminator.getTopic())
        .name(connectorDiscriminator.getValue())
        .endEvent()
        .done();

After we deploy the model instance created. Using the timerWithCycle we pass a timer repetitive timer like R2/2022-07-04T21:04:00Z/PT1M. We expect that two external tasks would be fired but instead we get three. Is this a known issue of the engine?