Not a developer? Go to



This is documentation about a configuration directive, which can be placed within Movable Type’s core configuration file, mt-config.cgi, to customize the behavior of the system.

Sets a limit, in seconds, on the amount of time that a given MT::TheSchwartz work_until_done loop should spend processing jobs in the publish queue.

When the MT::Schwartz object begins processing jobs, the epoch (a timestamp commonly used on UNIX-based computers) is recorded. After each MT::TheSchwartz::Job is marked complete or failed, the current time is re-checked. When the current time is more than SchwartzClientDeadline seconds after the moment that the loop was entered, work_until_done returns, allowing the calling process to proceed as if all jobs had been processed.

This will not interrupt any Schwartz tasks once they begin; SchwartzClientDeadline is only checked before beginning each subsequent Schwartz job.




  • integer (time in seconds, common values are 5 to 8 minutes or 300 to 480 seconds respectively)


If you want to specify that a Schwartz client should stop processing jobs after 300 seconds (5 minutes), use the following :

SchwartzClientDeadline 300