Job Resource reference error on subsequent order execution

Current Situation 

When using a Job Resource in a workflow, the issue occurs during execution of the second order. The workflow fails with the following error:

[Error], errorState=failed, code=UnknownKey, reason=disrupted, msg=No such JobResourcePath: JobResource:y
[OrderProcessed] id=#2026-01-27#F51318555600-y:New DOC Document - Copy.doc, Job=job, pos=0, Error (status=failed, code=UnknownKey, reason=disrupted, msg=No such JobResourcePath: JobResource:test)

Example :

• Two files are placed to trigger orders via a File Order Source.
• The first order executes successfully.
• The second order fails with unknown key for the Job Resource.

This issue does not occur consistently and is therefore difficult to reproduce reliably.

Please find attached controller and agent logs for reference.

Desired Behavior

All orders in the workflow should execute successfully, with the Job Resource remaining available and correctly referenced, without any unknown key errors.

Maintainer Note

When using the updated Controller, JobResources that are missing at the Agent should be redeployed with JOC. This fix does not repair a  situation where an Agent misses a JobResource. But this fix avoids the situation in the future.