Hi Camunda Team,
Would appreciate some hints on an error below which we never faced before. We’re using Camunda 7.16 version with Postgress DB.
Exception Trace Snippet:
Caused by: org.camunda.bpm.engine.ProcessEngineException: ENGINE-03004 Exception while executing Database Operation ‘UPDATE EverLivingJobEntity[0f477c3d-f39d-11eb-9e59-76d203510f29]’ with message ’
Error flushing statements. Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.JobEntity.updateEverLivingJob (batch index #1) failed. Cause: java.sql.BatchUpdateException: Batch entry 0 update ACT_RU_JOB
SET REV_ = 130557,
EXECUTION_ID_ = NULL,
LOCK_EXP_TIME_ = NULL,
LOCK_OWNER_ = NULL,
RETRIES_ = 3,
EXCEPTION_STACK_ID_ = NULL,
EXCEPTION_MSG_ = NULL,
FAILED_ACT_ID_ = NULL,
DUEDATE_ = '2022-05-11 00:01:00+00',
SUSPENSION_STATE_ = 1,
PROCESS_DEF_ID_ = NULL,
PROCESS_DEF_KEY_ = NULL,
JOB_DEF_ID_ = NULL,
DEPLOYMENT_ID_ = NULL,
HANDLER_CFG_ = '{"countEmptyRuns":0,"immediatelyDue":false,"minuteFrom":0,"minuteTo":59}',
PRIORITY_ = 0,
SEQUENCE_COUNTER_ = 13,
LAST_FAILURE_LOG_ID_ = NULL
where ID_= '0f477c3d-f39d-11eb-9e59-76d203510f29'
and REV_ = 130556 was aborted: ERROR: column "last_failure_log_id_" of relation "act_ru_job" does not exist
Position: 580 Call getNextException to see other errors in the batch.