Is it possible entry in act_ru_job table but not in act_ru_execution table?

in my case it is possible entry in act_ru_job table but not in act_ru_execution table.

Can you explain the situation in more detail?

in my case

Entry in job table

ID_ REV_ TYPE_ LOCK_EXP_TIME_ LOCK_OWNER_ EXCLUSIVE_ EXECUTION_ID_ PROCESS_INSTANCE_ID_ PROCESS_DEF_ID_ PROCESS_DEF_KEY_ RETRIES_ EXCEPTION_STACK_ID_ EXCEPTION_MSG_ DUEDATE_ REPEAT_ HANDLER_TYPE_ HANDLER_CFG_ DEPLOYMENT_ID_ SUSPENSION_STATE_ PRIORITY_ JOB_DEF_ID_ SEQUENCE_COUNTER_ TENANT_ID_
9805de63-3a2e-11eb-b9af-001dd8b71caa 1 message NULL NULL 1 98019892-3a2e-11eb-b9af-001dd8b71caa 98019892-3a2e-11eb-b9af-001dd8b71caa 68a1b88e-2f50-11eb-b9af-001dd8b71caa Rule_2343 3 NULL NULL 09-12-2020 14:55:36 NULL async-continuation transition-create-scope 689f95ac-2f50-11eb-b9af-001dd8b71caa 1 0 68a1b88f-2f50-11eb-b9af-001dd8b71caa 1 NULL

but in execution table not found any entry with job table execution id.

is it possible or not?

So job can be created and not yet be picked up by the engine or triggered (like in this case) my a BPMN message.

but execute this job throw exception like this.
org.camunda.bpm.engine.exception.NullValueException:
Cannot find execution with id ‘98019892-3a2e-11eb-b9af-001dd8b71caa’ referenced from job

Can you explain the details about how the error occurs?
The process in question, how you trigger the events etc.

configure with Embedded Process Engine

  • create process instance like this.

ProcessInstantiationBuilder process=runtimeService.createProcessInstanceByKey(“Rule_2343”);
process.setVariables(paramMap).execute();

Hi @nrpatel

You’ve added more details on a new thread - so i will lock this thread.