NullValueException: No job found with id

Camunda 7 Topics Discussion & Questions
1

We have the following error on our production:

ENGINE-16004 Exception while closing command context: No job found with id 828006d3-24c9-11f0-94cb-0a580a830363: job is null

Does someone know how this can happen?

Stack trace:

2025-04-29 09:45:31,644 ERROR [io-8080-exec-12] o.camunda.bpm.engine.context    : ENGINE-16004 Exception while closing command context: No job found with id 828006d3-24c9-11f0-94cb-0a580a830363: job is null
org.camunda.bpm.engine.exception.NullValueException: No job found with id 828006d3-24c9-11f0-94cb-0a580a830363: job is null
            at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
            at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
            at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
            at org.camunda.bpm.engine.impl.util.EnsureUtil.generateException(EnsureUtil.java:398)
            at org.camunda.bpm.engine.impl.util.EnsureUtil.ensureNotNull(EnsureUtil.java:55)
            at org.camunda.bpm.engine.impl.util.EnsureUtil.ensureNotNull(EnsureUtil.java:50)
            at org.camunda.bpm.engine.impl.cmd.GetJobExceptionStacktraceCmd.execute(GetJobExceptionStacktraceCmd.java:49)
            at org.camunda.bpm.engine.impl.cmd.GetJobExceptionStacktraceCmd.execute(GetJobExceptionStacktraceCmd.java:32)
            at org.camunda.bpm.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:28)
            at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:111)
            at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:70)
            at org.camunda.bpm.engine.impl.interceptor.CommandCounterInterceptor.execute(CommandCounterInterceptor.java:34)
            at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
            at org.camunda.bpm.engine.impl.interceptor.ExceptionCodeInterceptor.execute(ExceptionCodeInterceptor.java:55)
            at org.camunda.bpm.engine.impl.ManagementServiceImpl.getJobExceptionStacktrace(ManagementServiceImpl.java:251)
            at org.camunda.bpm.engine.rest.sub.runtime.impl.JobResourceImpl.getStacktrace(JobResourceImpl.java:63)
2

Hi @pme123

We sometimes have a problem like that, when e.g. we’re trying to modify a timer which was already due and meanwhile taken up by the job executor (and therefore the job was completed).
I would assume it could be something similar, where a job you’re trying to work with, was completed in the meantime and therefore doesn’t exist anymore in the database.

1 Like
3

thanks @rohwerj