This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

The Jobs engine is an Enterprise only feature, allows running CrushTask plugin based automation tasks, manually, scheduled in a timely fashion or triggered by user activity, when invoked as a user Event. It's a powerful feature offering advanced local or remote file processing capabilities, custom logging or sending out email notifications and some well beyond the scope of a MFT server application, like invoking a shell script, HTTP calls or SQL operations, IF/ELSE like decision making, text processing, etc. Our video tutorial covers the basics

http://www.crushftp.com/videos/jobs_events.mp4

The Jobs panel has three major sections, a list of available and active jobs, a designer panel and the scheduler.

Jobs list
#

Here can create new jobs and manage existing ones.

Available jobs
#

A list of existing jobs. In this section can create, clone or drop existing ones, using the New, Copy or Delete buttons. Selecting an entry in the list will open the job in the Designer window for editing.

Active jobs
#

A list of execution history, can filter on name, execution time interval and state (success,error) of a job. Selecting an entry from this list will open it in the Designer window.

with the processed items visible. The Log tab allows viewing and copying the log of this execution instance.

Designer
#

The main task flow editor window. Can add various task items by double clicking into the white space or dragging an item from the New Task icon. Most of the task items will have two connection nodes, a green and a red dot. Green path is taken on a successful execution of a task item. If it fails, the red dot path is followed, or if no error handling task flow connected, the job would fail with an error.

Scheduler
#

This page allows configuring the schedule execution time table and some other, more advanced configurations.

Save state between steps

Needed only when debugging with breakpoints, for normal operation mode, this option needs to be off

Logging enabled

toggles logging to file, on a per job basis

Save results of job at end

toggles saving jobs execution history, on a per jobs basis. If this option is not set, the job history won't show up in the Active jobs list

Only one instance running at a time

When toggled on, prevents overlapping schedules of the same job

Only one instance running at a time in cluster

In case of a HA server cluster, toggles running on the ServerBeat master node only. Has no effect without ServerBeat enabled

Users allowed to monitor

In case of a limited admin scenario, can pick a limited admin to be able to monitor this job.

Troubleshooting
#