Automated Workflows and Job Scheduling

Since 2000, Flux has proven itself as the backbone of many mission-critical applications across various industry sectors worldwide. Organizations seeking a feature-rich, highly-customizable platform that excels at time and event-based scheduling receive tremendous value from Flux's job scheduling software.

The Flux workflow engine supports simple or intricate automated workflows using a powerful state machine model. Define workflow steps that contain conditional branching, dependencies, looping, parallelism, splits, and joins. Perform tasks and wait for events to occur within your workflow.

Scale individual workflows to hundreds of steps. Run thousands of workflows across a cluster of Flux workflow engines. Invoke other workflows from within workflows.

You can define simple or detailed mechanisms to handle and recover from error conditions. Handling errors can be fully automated including sending notifications to people to take corrective actions.

Create workflows that depend on other workflows. Define workflows that wait for other workflows to reach milestones or to finish altogether. Create workflows that wait on and watch for files on FTP servers to arrive or change.

Design your workflows using a drag-and-drop visual interface, right in your web browser. No need to install a desktop client.

Look at your workflow dependencies – all within the browser.

To design multi-step workflows — complete with dependencies, conditional branching, and looping — you don’t need to be a software developer. (But if you want to use Flux’s full Java API, you can.)

Filter reports on different criteria, including workflow names, dates and times of events, message content, the Flux engine where events occurred, and more.

Create workflows that depend on other workflows. Define workflows that wait for other workflows to reach milestones or to finish altogether. Create workflows that wait on and watch for files on FTP servers to arrive or change.

Flux includes three different kinds of reports. The Audit Trail records significant events. The Run Report shows details on significant “runs” within a workflow. Logs show low-level details of running workflows.