You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
run --local boots with scheduled events disabled and prints nothing at start #1528
mxcli run --local boots with scheduled events disabled and prints nothing about it at start.
Repro
An app with a scheduled event. mxcli run --local --detach.
The runtime log shows Synchronizing scheduled events: None (disabled in configuration); the event never fires.
--runtime-setting ScheduledEventExecution=ALL fixes it.
Expected
Either the start summary says scheduled events are off and names the flag, or run --local documents or defaults it (the skill installed by mxcli init and run --help do not mention it).
Actual
Silent; the only trace is a runtime log line. In the v0.27.0 source --runtime-setting exists (cmd_run.go) and the string ScheduledEventExecution appears nowhere in cmd, mdl, internal or docs.
Tested with: Mendix 11.15.0, mxcli v0.26.0 on macOS; v0.27.0 source searched, not run.
Summary:
The mxcli run --local command starts the Mendix runtime with scheduled events disabled but gives no indication at startup, leaving users unaware that their events won’t fire.
Checklist (bug report)
✅ mxcli version (v0.26.0 mentioned)
✅ Mendix version (11.15.0)
✅ Scenario (running mxcli run --local --detach on an app with a scheduled event)
✅ Expected output (startup summary should note disabled scheduled events or the flag should be documented/defaulted)
❌ AI bug report / session log (output of mxcli diag --bundle or at least the session log)
Missing information:
Could you please provide the output of mxcli diag --bundle (or, if that’s not possible, the relevant session log) so we can see the exact environment and any additional context? Thank you!
Activity
github-actions commentedon Oct 16, 2026
Issue Triage
Summary:
The
mxcli run --localcommand starts the Mendix runtime with scheduled events disabled but gives no indication at startup, leaving users unaware that their events won’t fire.Checklist (bug report)
mxcli run --local --detachon an app with a scheduled event)mxcli diag --bundleor at least the session log)Missing information:
Could you please provide the output of
mxcli diag --bundle(or, if that’s not possible, the relevant session log) so we can see the exact environment and any additional context? Thank you!Automated triage via OpenRouter — workflow source
Merge pull request #1426 from ako/fix/1528-run-local-scheduled-events