When a Task is rejected by an agent due to a licensing issue the Agent URL is missing in the Scheduler History Table

Current Situation
When two tasks start at the same time and are supposed to run on the same agent and the agent licence allows only one task to run an error is thrown and the task is rejected by the agent.
Unfortunatly the entry in the SCHEDLUER_HISTORY table is missing the value for the AGENT_URL.

Impact
When the number of executed Tasks on an agent is counted, rejected tasks won´t be considered because they are missing the relation through the AGENT_URL field in the SCHEDULER_HISTORY table.

Desired Behavior
Even if a task is rejected by an agent, the AGENT_URL should be present in the SCHEDULER_HISTORY table.