Capabilities

Everything you expect from a commercial scheduler, organized so operators and administrators can both move fast.

Jobs & job groups

Nested groups pass down agent, calendar, timezone, time window, variables, owner and runtime settings. Override locally when you need to.

Calendars & fiscal calendars

Define eligible run dates, business periods, effective-date ranges and offsets. Reusable across many jobs.

Agents & agent lists

Distribute execution across machines. Agent lists give you failover and load spreading without extra tooling.

Dependencies & events

Prerequisites, job, variable, file and system events, and reusable actions build real workflows — not just isolated cron lines.

File events New

Watch a folder on any agent and fire when a matching file arrives, is rewritten in place, disappears or comes back. Then run an ordered list of steps: move, copy or rename the file, send it to another agent, run a command, start an orchestration, wait, or fire any action. Trigger one by hand to test it, and review every firing in its history.

System events New

React to the scheduler itself: compile started or finished, a new production day, master paused or resumed, a backup master taking over, a lost agent connection, an agent hitting its job limit. Each runs the actions you choose — email, alert, add a job, set a variable — and can be narrowed to one agent.

Browse agent file systems New

Pick files and folders by browsing the actual disk of the chosen agent, right from the File Mover, file event and orchestration forms. No more typing paths from memory.

Plugins & connections

Named, tested connections for SQL Server, REST APIs and more. Plugin jobs run in-process on the server or out on an agent.

Variables

Global, group and local variables inject into supported fields. Inherited values are visible before you override.

Workflow Designer

Visualize dependency chains with critical-path highlighting and an estimated duration. Drag new jobs and groups from a toolbox onto the canvas, move items between groups from a Definitions tree and rename them in place. Switch between list and flow views wherever relationships matter.

Live operations

Job Activity, Event Activity, Alerts, Logs, Schedules, Dashboard and Master Status — auto-refreshing counts of waiting, active and completed work. A waiting run says exactly why it waits, and a sequence check flags runs that started out of dependency order. Every job also keeps its own run history across production dates, and Orchestration Runs and log messages can be narrowed to a single day.

Access control & audit

Workgroup ownership, role-based permissions, LDAP sign-in, runtime users and an online-user indicator. A field-level audit log records every change and run status transition.

Orchestrations New

Pipelines over your existing jobs: conditions, loops, approvals, retries, sub-runs and values passed between steps. Build visually or in YAML, run on demand or on a cron schedule. See how →

CI/CD & DevOps New

Build, test and deploy on every git push: GitHub and GitLab webhooks, per-run workspaces, encrypted secrets, JUnit test results, artifacts, protected environments and status checks on the commit. See how →

Approval gates & branching

Pause a workflow until a named approver or workgroup approves or rejects it. Branch nodes pick the next job from the previous exit code — "= 0", "between 1 and 4", "≥ 8", or otherwise.

Resource pools & priority

Named limits such as "database connections: 4" that jobs and groups draw from. Higher-priority work is admitted first when capacity is tight.

SLA deadlines

"Finish within N minutes" or "finish by 06:00". A warning is raised at 80% of the window and a critical alert when the deadline is missed.

File Mover

Copy or move files of up to 10 GiB between agents. Stage, verify, back up and publish, stop and start services around a deployment, and recover safely if a delivery is interrupted. Administrators can require explicit per-workgroup folder grants for every transfer.

REST API & webhooks

Everything the console does is available over REST with revocable API tokens. Inbound webhooks let any system start one job or group, passing variable values for that run.

Version history

Save named versions of a whole job group, compare them field by field, preview a restore and roll back safely. Deleted definitions wait in a recycle bin.

AI assistance (optional)

Describe a job or a whole pipeline in plain English and review the proposed definition before saving. Failure alerts can carry a short explanation of the likely cause. Uses your own API key.

Schedule Simulator

Advance virtual time over a snapshot of your definitions to see what would run and when — without touching production.

Job iteration

One job definition fans out across a list of values — regions, file names, customers — instead of being copied once per value.

Export & import

Move definitions between IDRuns systems — from a file, or pulled directly from another live instance, with agent, owner and runtime-user names mapped on the way in. Test to production without retyping.

Automated import & migration services

Import Tidal definitions and, new, AutoSys JIL files automatically — ideal for demos, evaluations and proofs of concept. For a real production conversion we recommend our professional services team: they migrate job groups, calendars, agent lists, dependencies and variables for you, and review the result with you. Scoped as a services engagement.

Agent management & dependency mapping

The two things that make workload automation more than a fancy cron: knowing exactly what ran where, and knowing what has to finish before the next thing starts.

Agent management

Agents are small services you install on the machines where work actually happens. They call the server on a short interval to ask for work and report results — the server never calls the agent, so agents need no inbound network access and sit comfortably behind firewalls and NAT.

  • Heartbeat & health. Each agent has a name and sends a regular heartbeat. A machine that stops reporting is marked offline, and any in-flight runs on it are flagged so nothing waits forever.
  • Agent lists & failover. Group agents into a list and assign it instead of a single machine — IDRuns spreads load across the list and fails over automatically if one agent goes down.
  • Capacity controls. Cap how many jobs run at once, per agent and system-wide, so one busy day on one box doesn't starve the rest of the schedule.
  • Cross-platform & multi-tenant. Agents run on Windows and Linux, execute jobs as a chosen OS user, and a single agent can serve more than one IDRuns server.
  • Resilient delivery. If the server is unreachable when a job finishes, the agent holds the result and delivers it once the connection is back.
  • Live communication log. Each agent's Connections entry shows recent work sent to it and the results it returned — no separate log to tail.

Dependency mapping

Jobs rarely stand alone — a load has to finish before a report runs, a file has to land before it's processed. IDRuns models those relationships explicitly and lets you see them, not just configure them blind.

  • Workflow Designer. A visual canvas per job group showing every upstream and downstream dependency. Align horizontally or vertically, fit to page, and save the layout you land on.
  • Build in place. Drag OS, FTP, Plugin and Terminator jobs or job groups from the toolbox straight onto the canvas, and open any node to edit it without leaving the view. The Definitions tab shows the group tree: drop an item on a group to move it there, double-click to rename.
  • Prerequisites & events. Set prerequisite jobs on Dependencies, and reusable Actions and Job Events to trigger follow-up work when something completes, fails or is skipped. File Events and System Events start work when a file lands or the scheduler itself changes state.
  • List, Flow & Sequence views. Job Activity mirrors the same dependency graph live — switch views to watch the chain execute, not just how it was designed.
  • Dependency-aware sorting. Grids sort by dependency order by default; a sort-override indicator appears the moment a column sort would hide that order, so you can clear it and get back to the real execution sequence.
  • Inheritance-aware. Nested job groups pass down agent, agent list, calendar and time-window settings, so dependency chains stay consistent without repeating configuration on every child job.