MishaF

why is replace = "yes" a default behavior if it has such negative and mysterious implications?

is it possible to use https://www.sos-berlin.com/doc/en/scheduler.doc/xml/add_order-node_order_plugin.xml to add order to be executed at specific time (or delay)? If not, what is the way to do it?

In the current setup of the system, we have a lot of scheduled orders that reference business calendars as includes of live files in their schedules. The calendar files are generated daily. It was our observation (in v11 and v12) that the daily plan was not generating orders properly reflecting changes to the schedules. It was recommended that we ‘touch’ schedule files forcing re-read of the calendar information. In v13 we observe random disappearing of orders from the system. The workaround is to...

Andreas, maybe you can chime in on this... i got support folks fix the links to documentation, so now https://www.sos-berlin.com/doc/en/scheduler.doc/xml/add_order.xml page is visible. it says that there is a replace attribute replace="yes|no" (Initial value: yes) replace="no": Job_chain.add_order() will be called. replace="yes": Job_chain.add_or_replace_order() will be called. which says here https://www.sos-berlin.com/doc/en/scheduler.doc/api/Job_chain-javascript.xml#method__add_or_replace_order...

Confirmed in 1.13.8; bug had been filed.

is agent so stateless that it can respond to calls from different masters? or is this something that is not supposed to work at all?

i am doing a review of all jobs we had created. is there an advantage or disadvantage to running anything on master? should all jobs run on agents (and nothing on master)? any guidelines? cheers.

do you have a pid file leftover in the log directory?