Currently, Mendix Scheduled Events are configured statically in Studio Pro — we define the microflow, timing, and enable/disable status within the model itself. While this works for consistency, it becomes limiting when we have different needs across environments.
##The Problem:
Say in Dev or Test, we want the scheduler to run every 5 minutes for testing purposes. But in Production, the same event should run only once a day. Right now, we need to change the configuration in Studio Pro and redeploy the app — which is not ideal and creates unnecessary deployment overhead.
## Suggestion:
It would be great if Mendix allowed the scheduler’s timing and frequency to be configured per environment — either via:
Mendix Developer Portal (Environment Settings)
Or through environment constants / variables
##workaround:
currently i am creating a custom scheduler pattern that checks DB config before executing logic. But this adds extra logic, maintenance, and complexity that Mendix could easily avoid with native support.
Much Needed, I support this
I published a similar idea a while ago
https://community.mendix.com/link/space/scheduling-module/ideas/5129Idea
yes true, much needed.
Completely agree with this. Having to redeploy the entire app just to adjust Scheduled Event timings across environments is both inefficient and error-prone. Real-world scenarios often demand different scheduling patterns in Dev, Test, and Production — and managing this via Studio Pro creates unnecessary friction. The current workaround using database-driven configs works, but it's essentially reinventing the wheel and adds avoidable complexity.
Enabling environment-specific scheduling through the Developer Portal or environment constants would bring much-needed flexibility and align better with modern DevOps practices. This would make scheduled event management cleaner, faster, and far more maintainable across environments. Hope to see this on the roadmap soon!