Timer is triggered again after migration

Camunda 7 Topics Discussion & Questions
1

I have a process with a timer defined as PT10S, the process paused at T1.
After I migrated it to new version, the timer is triggered again, which was not expected.
I also noticed there was another job created for the timer, the timer.

image
image2487×1086 145 KB

I used migrationPlan as follows. Is there anything I’m doing wrong?

{
  "migrationPlan": {
    "sourceProcessDefinitionId": "Process_TestingAll:193:efb9cd33-687b-11ec-8552-00ff2f4282fe",
    "targetProcessDefinitionId": "Process_TestingAll:194:f369199d-687b-11ec-8552-00ff2f4282fe",
    "instructions": [
      {
        "sourceActivityIds": [
          "Activity_0a24ucn"
        ],
        "targetActivityIds": [
          "Activity_0a24ucn"
        ],
        "updateEventTrigger": false
      },
      {
        "sourceActivityIds": [
          "Event_04xluwx"
        ],
        "targetActivityIds": [
          "Event_04xluwx"
        ],
        "updateEventTrigger": false
      },
      {
        "sourceActivityIds": [
          "Activity_1sbe6nq"
        ],
        "targetActivityIds": [
          "Activity_1sbe6nq"
        ],
        "updateEventTrigger": false
      }
    ]
  },
  "processInstanceQuery": {
    "processDefinitionId": "Process_TestingAll:193:efb9cd33-687b-11ec-8552-00ff2f4282fe"
  },
  "skipCustomListeners": true
}

Process_TestingAll.bpmn (4.9 KB)

2

Hi,

Was there any instance pending for previous version, when you migrated for new one?

Thanks
Anmol

3

Hello Anmol,

There is only one process instance, which I posted above. And this process definition is dedicated for testing.