When scheduler.order.keep_order_content_on_reschedule="false" previous set parameters exist after JobScheduler-Restart

We have ...

• parameter scheduler.order.keep_order_content_on_reschedule="false" in the ./config/scheduler.xml
• a job chain with more than one node and orders_recoverable="yes"
• an order without parameter
• the first job adds a parameter to the order
• the second job adds a parameter to the order
  See attachment.

The first new parameter is stored in the db table SCHEDULER_ORDERS after the first node is finished.
The second new parameter does not be stored in the db table SCHEDULER_ORDERS because the job chain end is reached and the order goes to its initial state (normally the begin of the job chain) without parameter (scheduler.order.keep_order_content_on_reschedule="false").
So far so good.

Now the record which was written after the first node is still in the SCHEDULER_ORDERS. This has the effect that the order gets this parameter after a JobScheduler restart.

TODO:
When scheduler.order.keep_order_content_on_reschedule="false" is set, the order in the job_chain never starts with order-parameters set at the last run of the order.
This is true even after a restart of JobScheduler.