-
Bug
-
Resolution: Done
-
Major
-
7.59.0.Final
-
None
-
None
-
False
-
None
-
False
-
NEW
-
NEW
-
---
-
---
-
-
For process with several timers, PUT /timers will try to delete the old timer based on timer.getTimerId() not timer.getId() which ends into no timer being deleted (sometimes timerId =0) or wrong timer deleted (if you update timer id=2 with timerId=1 and there's a timer id = 1:
{
"timer-instance": [
{
"name": "HT1-timer1",
"id": 2,
"timer-id": 1,
"activation-time": "2023-09-15T02:56:41.378+0200",
"last-fire-time": null,
"next-fire-time": "2023-09-15T02:58:41.378+0200",
"delay": 120000,
"period": 0,
"repeat-limit": -1,
"process-instance-id": 31,
"session-id": 116
},
{
"name": "HT2-timer2",
"id": 1,
"timer-id": 1,
"activation-time": "2023-09-15T02:56:41.341+0200",
"last-fire-time": null,
"next-fire-time": "2023-09-15T03:00:41.341+0200",
"delay": 240000,
"period": 0,
"repeat-limit": -1,
"process-instance-id": 31,
"session-id": 116
}
]
}
What is timerId used for?
- is depended on by
-
-
- Release Pending
-
