Previously, the scheduler flows were visible under Runtime Manager → Schedules in both QA and Stage environments.
The issue started after a recent deployment that included application changes.
Since that deployment, the scheduler UI no longer displays any schedulers in QA and Stage.
The same application is still executing scheduled jobs successfully, and scheduler logs are visible.
The Demo environment continues to display schedulers correctly in the Scheduler UI.
#MuleSoft Anypoint Platform
Hi Jakeer!
Since the schedulers are still executing successfully and the logs are present, this looks more like a CloudHub 2.0 Runtime Manager UI/metadata issue than the scheduler itself being disabled.
Because it started immediately after a deployment, I’d compare the deployed application configuration between Demo, QA, and Stage, especially the scheduler configuration in the Mule application properties and the deployed artifact.
A few things I’d check:
- Confirm the scheduler flows are still packaged in the deployed artifact.
- Compare the scheduler-related configuration/properties between Demo, QA, and Stage.
- Check whether the deployment changed the application name, environment, or runtime version.
- Redeploy the same artifact/configuration to QA and see whether the schedulers reappear.
- Check Runtime Manager/API responses for the application rather than relying only on the UI. If the scheduler metadata is returned through the API but not displayed in Runtime Manager, that would strongly point to a UI/metadata issue.
Since the jobs are actually running, I’d avoid changing the scheduler configuration just to fix the UI until you confirm whether the schedules are missing from Runtime Manager itself or only from the Scheduler page.
If you can share the Mule runtime version, deployment method, and whether the QA/Stage deployments use the exact same artifact as Demo, that would help narrow it down.
