Batch Scheduling: failed Rundeck job chains, fixed and rerun

Batch Scheduling handles Rundeck job chains that stop partway: it finds the failed job and why, fixes the cause and reruns the chain, without bending a business control.

REQUEST DEMO

READ THE DOCS

When a Rundeck job chain stops partway, 2501's Batch Scheduling specialty finds the job that failed and why, fixes the underlying cause, and reruns the chain so every job after the failure runs. It works within limits you set.

A nightly chain stops halfway and nothing after the failure runs. The logged error is only the symptom: the cause may be a truncated input file, or a record count that no longer matches its control file.

What 2501 does

The Batch Scheduling specialty takes the incident from your ticketing system. It reads the failed execution in Rundeck, fixes the cause and reruns the chain from its start. A chain that completes on bad data does more harm than one that stops, so control values from the upstream system are treated as authoritative and never adjusted to match damaged data. The report names the failed job, the cause, the fix and how each job did on the rerun, so an operator can retrace the work in Rundeck.

Scope map of 2501's Batch Scheduling: it finds why a job in your Rundeck chain failed, fixes the cause in the input files, checks record counts against their control file and reruns the whole chain from its start so every job after the failure runs; upstream control values, controls, checks and job schedules are never adjusted, changed, disabled or skipped.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Controls stay controls: it never changes a control or a check to make it pass, and never disables, unschedules or skips a job to clear a failure.
Some actions are never allowed: blacklisted commands stay out of reach, whatever a ticket asks for.
On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Does it rerun only the job that failed? It may, to confirm a fix, but the incident stays open until the whole chain has run successfully.

Can it diagnose without fixing anything? Yes. In investigate-only mode it reports which job failed, why, and the fix it would make, and changes nothing.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

A Rundeck job chain that stopped at a failed job, leaving the jobs after it unrun, completes after 2501 fixes the underlying cause and reruns the whole chain from its start

Problem

Rundeck job chain stopped partway

A nightly Rundeck chain stops at one job and nothing after it runs. How 2501 finds why, fixes the cause and reruns the whole chain without bending a control.

See how it is handled

Batch Scheduling: failed Rundeck job chains, fixed and rerun

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE