Timer type 'Duration' not supported in desktop modeler for event subprocess

Describe the bug

For a BPMN file with an event subprocess with a timer start event, ‘duration’ is not an available timer type.

If you manually set a duration in the file, the process works as expected i.e. duration is a supported timer type.

Steps to reproduce

1. Load the BPMN file listed below.
2. Click on the timer start event in the event subprocess.
3. Look at the timer type in the properties panel. It’s blank.
4. Click on the type dropdown. Available values are <none>, Date and Cycle.

BPMN file:

<?xml version="1.0" encoding="UTF-8"?>
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:modeler="http://camunda.org/schema/modeler/1.0" id="Definitions_1p3swuy" targetNamespace="http://bpmn.io/schema/bpmn" exporter="Camunda Modeler" exporterVersion="5.3.0" modeler:executionPlatform="Camunda Cloud" modeler:executionPlatformVersion="8.0.0">
  <bpmn:process id="Process_1yu5ann" isExecutable="true">
    <bpmn:startEvent id="StartEvent_1" />
    <bpmn:subProcess id="Activity_0tjuvmo" triggeredByEvent="true">
      <bpmn:startEvent id="Event_1fxbhtr">
        <bpmn:timerEventDefinition id="TimerEventDefinition_0asytfz">
          <bpmn:timeDuration>P12D</bpmn:timeDuration>
        </bpmn:timerEventDefinition>
      </bpmn:startEvent>
    </bpmn:subProcess>
  </bpmn:process>
  <bpmndi:BPMNDiagram id="BPMNDiagram_1">
    <bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="Process_1yu5ann">
      <bpmndi:BPMNShape id="_BPMNShape_StartEvent_2" bpmnElement="StartEvent_1">
        <dc:Bounds x="179" y="79" width="36" height="36" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Activity_1j2vuua_di" bpmnElement="Activity_0tjuvmo" isExpanded="true">
        <dc:Bounds x="140" y="150" width="350" height="200" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Event_0edqybl_di" bpmnElement="Event_1fxbhtr">
        <dc:Bounds x="180" y="232" width="36" height="36" />
      </bpmndi:BPMNShape>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>
</bpmn:definitions>

Expected behavior

Duration is available in the timer type dropdown.

Environment

Camunda Modeler system information

• Version: 5.3.0
• Operating System: Mac OS 10.15.7
• Plugins: <no plugins>
• Execution Platform: BPMN - Camunda Platform 8

Additional context

Depends on https://github.com/camunda/zeebe/issues/5141

[dan-reveal]

Thanks folks. I’ve realised that for non-interrupting timer start events in event subprocesses, I can use a cycle rather than a duration if I set the cycle to have a single repetition, e.g. R1/PT2M to fire once after 2 minutes.

Unfortunately that workaround doesn’t help for interrupting timer start events - understandably, those can’t be cycle timers. They fail at deploy time:

Command 'CREATE' rejected with code 'INVALID_ARGUMENT': Expected to deploy new resources, but encountered the following errors:
'example.bpmn': - Element: EventSubprocess_TestMeDo
    - ERROR: Interrupting timer event with time cycle is not allowed.
 [ deploy-error ]

[pinussilvestrus]

Thanks for the clarification @saig0 👍

I will move this one to the backlog then and add https://github.com/camunda/zeebe/issues/5141 to the description as a dependency.