Find the right fit
for your workflows.

Readable recurrence, supported five/six-field cron and explicit timezone/DST policies.

Scheduled and event-driven workloads; exact dialect depends on configuration.

Date/time and event-driven triggers.

One-off and recurring script execution.

Scheduling, calendars, timezones and forecasting.

Recurrence triggers; workflow/hosting model determines limits.

Scheduled and signal-triggered automation in current platform brief.

Schedule and on-demand initiation in the vendor feature guide.

External trigger keys, file/directory watchers and task-completion sources.

Event-driven workload initiation.

Event-driven scheduling and automation triggers.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Events coordinate job prerequisites.

Event triggers and connector actions.

Monitoring, ITSM and other event signals can start workflows.

File-arrival dependencies and external events can initiate RPA jobs; MFT cloud triggers and VisualCron require their integrations.

Durable success/failure/any completion chains; no claim of a full visual branching workflow language.

Workload orchestration and dependencies are described by the platform.

Multi-step job orchestration and reusable job steps.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Job dependencies and prerequisites.

Visual workflows composed from triggers and actions.

Conditional and parallel workflow composition in the platform brief.

Job-status dependencies and conditional initiation are documented in the VisualCron RPA integration context.

Wails desktop, gosched CLI and versioned JSON API; specific CLI gaps remain tracked.

Web/thick clients and .NET/REST interfaces.

Console/web/self-service interfaces and integration API.

Portal and REST/Swagger integration.

Web interface and Jobs-as-Code CLI/API.

Visual designer and code/deployment tooling.

Visual/API authoring and script/SSH/CLI capabilities.

Official CLI integration manages machines, jobs and schedules through REST; this cell establishes CLI/API access.

Explicitly enrolled independent daemons, All Systems, search and portable configuration.

Cross-platform execution and agents.

Integration across supported infrastructure and applications.

Remote script execution through the platform.

Central workflow orchestration spans platforms, applications and infrastructure; self-hosted and SaaS contexts differ.

Azure/on-premises integration; hosting model matters.

Automation across systems through integrations and remote execution.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Execution history/logs, webhook delivery and desktop notifications; SMTP is planned separately.

Monitoring and email notifications.

Monitoring, reporting and SLA functions.

Audit and reporting for script operations.

Monitoring and operational job views.

Workflow run monitoring and diagnostic integration.

Operational/audit information in the current platform brief.

Versioned v26.0 history management.

Actor capabilities, delegated credentials and management audit records.

Object ACLs and centralized execution credentials are documented; this evidence does not establish every audit scope.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Role-based access and managed credentials.

Roles limit interface, folder, job and operation access; audit coverage needs separate evidence.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

REST access, role-based control and audit.

Role-controlled history management is documented; other scopes need version-specific review.

Optional local and authenticated remote MCP with explicit authority.

Current vendor platform advertises MCP; edition/availability should be checked.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

9.0.22 documents a preview MCP server with API-version prerequisites and request/client limits; BMC recommends non-production use.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Independent-daemon management does not provide clustered execution ownership/failover.

A separate failover scheduler takes over after missed heartbeats; jobs running locally on the failed scheduler can still fail.

Platform overview describes failover; edition/deployment context applies.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Self-hosted secondary-server failover is documented; automatic versus manual takeover depends on database topology.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Apache 2.0 source; locally operated daemons without a hosted account requirement.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

Azure service with Consumption, Standard and hybrid deployment distinctions.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.

The cited overview does not establish this capability for the selected edition; consult the vendor before deciding.