If expiration time of a job already passed then error is thrown in Jobs service. This is an incompatibility with 7.x jBPM executor, where job with passed execution time is executed immediately.
I would expect the job executor to have same behaviour for this case as jBPM executor.

This could also become tricky in OpenShift environment where Job service can be located on node with different time zone than Kogito engine.