What happens when you enable CRON in the scheduler?

What happens when you enable CRON in the scheduler?

• A. The scheduler stops
• B. You can see the application on Cloud Hub and trigger it in the runtime manager
• C. The app is deleted from CloudHub
• D. It triggers instantly with no config

Answer: (B)

Enabling CRON in the scheduler creates a time-based trigger for your deployed flow. Once it's turned on, the application appears in CloudHub, and you can trigger a run manually from the Runtime Manager to test or execute the scheduled process on demand. The cron schedule then governs when automatic executions happen, rather than happening immediately with no configuration. So this setup lets you see the app in CloudHub and have a manual trigger available in Runtime Manager, rather than stopping the app, deleting it, or firing instantly without any schedule.

Enabling CRON in the scheduler creates a time-based trigger for your deployed flow. Once it's turned on, the application appears in CloudHub, and you can trigger a run manually from the Runtime Manager to test or execute the scheduled process on demand. The cron schedule then governs when automatic executions happen, rather than happening immediately with no configuration. So this setup lets you see the app in CloudHub and have a manual trigger available in Runtime Manager, rather than stopping the app, deleting it, or firing instantly without any schedule.