I’m having a few problems with Timer Delays. In this example, I have 2 Timers set for Durations Type.
This is an HR process to schedule a Candidate for an interview. The Candidate is assigned a User Task which displays a URL to Schedule their interview, but oftentimes the Candidate will click the URL & and forget to complete the User Task.
So in this case, if the Candidate forgets to complete the User Task, it will timeout after 15 mins and move on to the next task.
In the second Time Delay, I want to have a Timer Delay to give the Candidate time to schedule their Interview before HR checks the Calendar. So there is a 10 Hour Delays before HR is tasked with checking the Calendar to verify.
Our Delays seem to be getting stuck and never trigger so I’m not sure what I’m doing wrong.
I was using “PT15M” and “PT10H” but have changed these to “P15M” and “P10H” for testing.
Can you guys have a look and tell me what I’m doing wrong?
I feel like it might never have worked so I check if the setting was configured and I did not see the setting for JobExecutorActivate in the bpm-platform.xml so I added the setting and restarted the server.
Should it automatically start processing the delays upon restart or do I need to do something to get them to retry?
Hmmm, Ok I’m pretty sure the Job Executor is enabled now and I’m showing this in the logs to confirm.
21-Oct-2020 05:59:15.949 INFO [Thread-6] org.camunda.commons.logging.BaseLogger.logInfo ENGINE-14018 JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor] starting to acquire jobs
However, when I created a new process and waited a decent amount of time that should have trigger the 15 min delay, nothing seems to have happened.