I tried to find a solution in existed topics but couldn’t so I hope you can help me with my issue.
I have several timers in my flow but if some timer due date goes to the next months, the system calculates due date from the first date of month, not from timer creation date.
Timer creation date: 28.10.2022
Timer definition type - duration and definition R/PT168H (7 days)
Expected Timer due date: 02.11.2022
Actual Timer due date: 08.11.2022 (01.11.2022 + 7 days)
I’m not sure it’s correct behaviour. Is it a bug or I should change in my flow something?
It should be one time. But I don’t think it influences this issue. It happened only for timers from October to November. I have flows where a timer goes from November to December and everything calculates correctly
Is it possible to start process in tests in the past? I tried to catch this bug by creation timers that goes to May (after changing winter time to summer) but everything works properly.
And I can’t reproduce this particular bug due to Camunda doesn’t provide possibility to set start process date, so I can’t set start date as October. Can I do this through API for example?
Thank you in advance.