BMPMN flow failing when using a timer


#1

Hi I have an issue with a BPMN flow failing for me only when i use a timer event.
the.
Deploying it within a springs boot application , per cockpit logs it errors out with ‘org.camunda.bpm.engine.ProcessEngineException: Unknown property used in expression: ${validateBANDelegate}. Cause: Cannot resolve identifier ‘validateBANDelegate’’
final line printer before the error is ENGINE-14008 Adding new exclusive job to job executor context.
Job Id=‘74436’
this happens in 7.5 and 7.8 versions of cumunda, the failure only occurs when timer attempt to direct control to the next service task.
can some please take a look and advice of the best possible course to sort this issue out.

BillingOTCFlow.bpmn (11.3 KB)


#2

I am also facing the same exact issue
Were you able to fix it ?


#3

Hi @Vernon,

do you deploy the BPMN process as part of the process application?
Do you use the Camunda Spring Boot starter?

Please verify that the process engine configuration property ‘jobExecutorDeploymentAware’ is set to true.

Best regards,
Philipp


#4

Even I am facing the same issue, we have a Intermediate timer catch event with no delegate handler its juts suppose to wait but I get same issue like mentioned by vernon.

and I can confirm that we have jobExecutorDeploymentAware set to true and also we are not doing any deployment using REST service.

do you deploy the BPMN process as part of the process application? - Yes
Do you use the Camunda Spring Boot starter? - Yes

Camunda version is 7.7


#5

Hi @prakash_choudhary,

just to make sure, do you use only the Camunda Spring Boot starter without any other process engine (e.g. the Camunda Tomcat distro) ?

Can you reproduce the issue in a test case?

Best regards,
Philipp


#6

Hi @Philipp_Ossler,

Strange thing is we don’t face that issue all the time, it starts coming randomly and the after that we get that error for all new jobs that gets invoked, and then when we deploy the same application in other environment it gives no error and all back to normal. So may be the environment can cause an issue but unable to come up with a solid reason.

Also when we face this incident we see incident reported only in cockpit but we don’t see any kind of error log in our log files.

Regards,
Prakash