Calendar Scheduling
Create business calendars with explicit dates and operational windows, then attach them directly to workflow triggers.
Product / Batch Job Processing
Batch Scheduling with Orchestration
Unmeshed orchestrates batch workloads through workflow definitions that support calendars, cron triggers, complex inter-process dependencies, script execution, and operational state controls.
05:00
05:01
05:02
05:03
warehouse_nightly_load
05:04
05:05
partner_file_ingest
05:06
05:07
invoice_settlement_post
05:08
05:09
eod_reconciliation_run
05:10
05:11
compliance_report_gen
05:12
05:13
payroll_batch_close
05:14
05:15
warehouse_nightly_load
05:16
05:17
partner_file_ingest
05:18
05:19
invoice_settlement_post
05:20
05:21
eod_reconciliation_run
05:22
05:23
compliance_report_gen
05:24
05:25
payroll_batch_close
05:26
05:27
warehouse_nightly_load
05:28
05:29
partner_file_ingest
05:00
05:01
05:02
05:03
warehouse_nightly_load
05:04
05:05
partner_file_ingest
05:06
05:07
invoice_settlement_post
05:08
05:09
eod_reconciliation_run
05:10
05:11
compliance_report_gen
05:12
05:13
payroll_batch_close
05:14
05:15
warehouse_nightly_load
05:16
05:17
partner_file_ingest
05:18
05:19
invoice_settlement_post
05:20
05:21
eod_reconciliation_run
05:22
05:23
compliance_report_gen
05:24
05:25
payroll_batch_close
05:26
05:27
warehouse_nightly_load
05:28
05:29
partner_file_ingest
Scheduling Intelligence
Combine calendar logic with cron and intervals so workflows align to business timing and runtime constraints.
Code Calendars
Define generated calendars by expressions and compose union/intersection behavior for advanced scheduling logic.
Cron and Interval Triggers
Run by cron patterns or fixed cadence for predictable recurring workloads and intraday execution cycles.
Reschedule and Carryover
Control non-working day behavior by rescheduling to previous/next eligible execution windows.
Workflow Definition Model for Batch
Workflow Definitions First
Batch jobs are orchestrated through workflow definitions, not isolated scheduler entries. Trigger logic, dependencies, and fallback paths stay explicit and versionable.
Dependency Mapping
Express inter-process dependencies such as wait-for-completion conditions, branch gates, and multi-step fan-in/fan-out behavior.
Scripting + Command Execution
Run scripts and commands as orchestrated steps with consistent controls, retries, timeout policy, and execution context.
Agent Execution Fabric
Orchestrated workloads can dispatch command execution across multiple agent targets while retaining centralized control and observability in the workflow runtime.
Linux Agent
Run shell commands and script-based workload steps on Linux hosts from workflow-driven schedules and dependencies.
Windows Agent
Execute command and script steps on Windows environments with the same orchestration controls used across all platforms.
IBMi / AS400 Agent
Coordinate legacy platform workloads through workflow definitions so critical enterprise jobs stay visible and governable.
How Agent Execution Works
Trigger
Workflow starts from calendar, cron, or event trigger.
Dependency Check
Dependency rules determine which agent-side job runs next.
Agent Run
Target agent executes command/script step and returns status.
Logs + State
Success/error logs and outputs are captured in dashboard state.
State Management Options
Batch workflows need durable state for retries, delayed continuations, and cross-step data access. Unmeshed supports multiple state handling patterns for different workload needs.
State Patterns in Batch Orchestration
Persisted workflow state for long-running and restart-safe execution
Managed data stores for shared operational context
Run-scoped variables for step-to-step data propagation
Execution logs and outcomes retained for audit and support workflows
Production Operations Console
Centralized Agent Logs
Agents report success and error logs to the dashboard so teams can troubleshoot runs without logging into each client machine.
Run Timeline + Metrics
Track execution duration and trend distributions with percentile views (P50, P90, P95) to spot bottlenecks early.
Pause / Retry / Rerun
Operators can pause execution, retry from failure points, and rerun workflows with controlled context.
Alerts and SLA Guardrails
Detect SLA drift, stalled dependencies, and repeated failures with policy-aware monitoring and escalation paths.
Runtime Intervention Controls
Batch operations teams can intervene safely in active workflows using hold and skip controls, without losing orchestration context.
Process Hold Steps
Pause selected workflow steps during active batch runs to safely control execution while investigations or approvals are in progress.
Read how-to guideProcess Skip Steps
Skip specific workflow steps when needed to recover blocked executions and continue delivery without restarting the full process chain.
Read how-to guideMigration Playbook from Legacy Schedulers
Execute phased migration from AutoSys-style environments with parity validation and low-risk cutover sequencing.
- Inventory existing AutoSys or legacy scheduler job sets, calendars, and job dependencies.
- Map current semantics into workflow definitions with explicit trigger and dependency rules.
- Run parity validation in parallel windows before cutover by workload family.
- Promote in controlled phases with rollback runbooks and ownership by domain.
High-Impact Batch Use Cases
Nightly data lake/warehouse pipelines
Coordinate extraction, transform, validation, and publish stages.
Financial settlement and reconciliation cycles
Enforce cutoff windows, retries, and controlled exception handling.
Partner file exchange and ingestion chains
Trigger processing on arrival and route failures deterministically.
Cross-environment batch release automation
Promote and verify job bundles across environments safely.
Infrastructure and platform maintenance windows
Run patch and maintenance jobs in approved execution windows.
Compliance and end-of-day operational reporting
Generate audit-ready reports from workflow-backed run records.
Modernize Batch Without Losing Operational Control
Start with one workload family, validate execution parity, then scale orchestration standards across your batch estate.