Hi,
We did a below setup to trigger a process model once for every 2 weeks on Tuesdays. Everything was working.
One fine day we did some changes to the process model and deployed during weekend we expected the process model will trigger. But, it did not trigger.
Question: Process Model will count the weeks starting from the day when we did re-deployment? will it not remember initial processed day/week and trigger accordingly.
Discussion posts and replies are publicly visible
You define the first period after deployment using the "Scheduled Delay". The recurrence starts after that initial delay.
I thought process model will run as per the schedules irrespective of n-number of deployments in between. But, it is not behaving like that.
Any further help on this.
A typical approach is to add a XOR node to check that the initial run does not occur at a bad date.
I have selected the option "Delay until the date and time specified by this expression and I have specified not to start until 7/17/2023 and it worked well during my initial deployment.
Now the issue is, I have done deployment recently after some business logic changes and I have expected that it will run as per the schedule, but it did not ran.
It should run, I couldn't see any issue with your configuration. Have you noticed that the process instance of this model got triggered as expected after the deployment?
Process model did not run as per schedule after my deployment.
Is there any .conf file or any other file where I can find the details about these schedule timelines.