Recommended Free Tools
You can run a scheduled Mule flow immediately from CloudHub 2.0 Runtime Manager’s Schedules view. For the original CloudHub generation, the management API documents an operation to run schedules. These are different deployment generations with different API families: do not use the legacy CloudHub schedules API for CloudHub 2.0. In CloudHub 2.0, a Schedulers API PUT changes schedule settings; it is not the same operation as running a job now.
First identify which CloudHub generation hosts the application
The deployment generation determines which controls and API family apply. CloudHub and CloudHub 2.0 schedule management are not interchangeable.
| Deployment | Run a scheduled flow now | Change or control the schedule |
|---|---|---|
| CloudHub 2.0 | Use Runtime Manager’s Schedules view to run the scheduled job immediately. The available documentation does not establish a specific API endpoint or request for an immediate run. | Use the CloudHub 2.0 Schedulers API for supported schedule overrides, or Runtime Manager to inspect and control schedules. |
| CloudHub (first generation) | The CloudHub management API documents an operation to run schedules. | The legacy management API documents schedule update, enable, and disable operations. It does not expose CloudHub 2.0 scheduler or domain details. |
Do not copy an endpoint from one generation into the other. The available documentation establishes the API families and operations, but not the exact request URLs, authentication details, or payloads for invoking a run-now operation. Consult the API reference for your deployment generation before constructing a request.
Run a CloudHub 2.0 scheduled job immediately
- Open the application in Runtime Manager. Select its Schedules view to see the Scheduler components in the deployed flows.
- Choose the scheduled job and run it. Runtime Manager lets operators run a scheduled job immediately without changing the running application’s configuration.
- Check the flow’s effects and logs. Confirm that the intended work occurred, particularly if an automatic scheduled invocation could overlap with the manual run.
Viewing schedules requires Exchange Viewer and Read Applications permissions. If the Schedules view is unavailable, check that your account has both permissions.
#1 Best Overall
What the CloudHub 2.0 Schedulers API changes
The documented CloudHub 2.0 Schedulers API supports PUT overrides for schedule properties. It does not make a schedule run merely because an override was submitted.
- Fixed-frequency Scheduler: override
frequency,startDelay, ortimeUnit. - Cron Scheduler: override
expressionortimeZone. - Restore application settings: delete the override to return to the schedule configuration in the application.
Use an override when you need to adjust when future scheduled executions occur. To launch work immediately in CloudHub 2.0, use the documented Runtime Manager run-now control; do not treat a timing override as an invocation request.
Run schedules through the original CloudHub management API
For first-generation CloudHub, the management API documents operations to update, enable, disable, and run schedules. Use the documentation for that generation to identify the applicable resource and request format; those details are not established here. The legacy schedules REST API is not the API for CloudHub 2.0 scheduler or domain details.
Choose fixed frequency or cron for recurring execution
A Scheduler is a Mule event source at the start of a flow. It can run at a fixed frequency or according to a Quartz cron expression. Fixed frequency suits regular intervals; cron suits calendar-based timing and can specify a time zone.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
Fixed-frequency schedules
Frequency is an interval setting rather than a calendar rule. In CloudHub 2.0, its API override can include frequency, startDelay, and timeUnit. A rolling restart can cause a fixed-frequency schedule to lose its prior cadence anchor and recalculate from polling-node election, so do not assume its earlier interval timing remains anchored across that event.
Cron schedules and time zones
A cron expression has six required fields—seconds, minutes, hours, day of month, month, and day of week—and an optional year. CloudHub uses UTC by default for Scheduler execution. A cron Scheduler’s timeZone can specify another Java time-zone value; account for that explicitly when a schedule is intended to follow local civil time rather than UTC.
Understand which replica executes a schedule
Scheduler execution depends on runtime topology, and duplicate processing is a design risk if more than one replica can run the same work.
- Mule runtime cluster or multi-worker CloudHub deployment: the Scheduler executes only on the primary node.
- CloudHub 2.0 clustered application: one primary replica runs a schedule.
- CloudHub 2.0 non-clustered application with multiple replicas: scheduled jobs can run on all replicas. Multiple concurrent schedules may be distributed across replicas.
Make scheduled processing idempotent where possible, and use application-level safeguards when duplicate work would cause damage. Do not infer from “one schedule” that a non-clustered multi-replica deployment necessarily means one execution.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Control overlapping invocations
CloudHub 2.0 schedules run concurrently by default. If a second invocation must wait until the previous one finishes, set disallowConcurrentExecution=true. This addresses overlapping executions of the Scheduler; it is not a substitute for idempotency or duplicate protection across replicas.
Plan for skipped or delayed runs
Back-pressure
If Mule has no resources available when a scheduled trigger occurs, the Scheduler skips that execution. A skipped trigger is not evidence that the flow will be replayed later.
Application stopped at trigger time
In CloudHub 2.0, if the application is not running when a schedule is due, the missed execution is not immediately replayed at startup. The schedule waits until its next scheduled time.
Maintenance and replica replacement
During certain CloudHub 2.0 infrastructure updates, the platform waits five minutes for existing schedules. After a new replica launches, a schedule runs at its next scheduled time. This behavior, together with the fixed-frequency cadence recalculation during rolling restarts, means a schedule should not be treated as a durable queue of missed work.
Quick Recap
Operational checklist before relying on run-now
- Confirm whether the application is on CloudHub or CloudHub 2.0, then use the matching API family or Runtime Manager control.
- Separate an immediate invocation from an override to a recurring schedule’s timing.
- Check whether the schedule can execute on multiple replicas and whether concurrent runs are allowed.
- Make the flow safe against retries, manual runs, and duplicate processing.
- Decide how the business process detects and recovers work skipped during back-pressure, downtime, or infrastructure changes; the Scheduler does not immediately replay missed CloudHub 2.0 executions.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
