look for a log in SCHEDULER_ORDERS first before looking in SCHEDULER_ORDER_HISTORY when serving http://host:port/show_log?job_chain=jobkette&order=order_id

If a Job Scheduler tries to show the log of an order which it is not currently executing (e.g. a waiting distributed order or a distributed order on another Job Scheduler), it will try to read the log from SCHEDULER_ORDER_HISTORY. This will either result in:

• No log at all, if the order hasn't finished (--> not entry in SCHEDULER_ORDER_HISTORY)
• The log of a previous order with the same id (Scheduler finds old log in SCHEDULER_ORDER_HISTORY)
• The correct log, if the order has finished

Looking in SCHEDULER_ORDERS first will enable the Job Scheduler to serve the correct log