Repository navigation
System Java actions are unknown to mxcli #1445
Description
Environment
- mxcli: v0.26.0 (release binary, 2026-10-11)
- Mendix version: 11.13.0 (blank app from
mxcli new R --version 11.13.0 --theme none --skip-init) - OS: Linux x86_64 cloud container (no Studio Pro;
mx/mxbuild only) - Also seen on: GenAI Showcase (mendix/genai-showcase-app) 11.12.0
Summary
System.VerifyPassword is listed by list java actions but describe java action and exec cannot look it up, so a valid call prints a warning and builds its entity type parameters as empty.
Reproduction
$ mxcli -p R/R.mpr -c "list java actions in System"
| Qualified Name | Module | Name | Folder |
|-----------------------|--------|----------------|--------|
| System.VerifyPassword | System | VerifyPassword | |
(1 java actions)
$ mxcli -p R/R.mpr -c "describe java action System.VerifyPassword"
Error: java action not found: System.VerifyPassword
-- u53.mdl
mdl 1;
create microflow ModA.MF_A ($User: System.User) returns boolean as $Ok
begin
$Ok = call java action System.VerifyPassword(userName = 'a', password = 'b');
return $Ok;
end;
mxcli check -p R/R.mpr u53.mdl prints Check passed!; mxcli exec -p R/R.mpr u53.mdl:
Connected to: R/R.mpr (Mendix 11.13.0)
2026/10/12 11:36:21 warning: could not look up Java action System.VerifyPassword: java action not found: System.VerifyPassword (entity type params will be empty)
Created microflow: ModA.MF_A
Expected
System Java actions resolve like module ones; no warning on a valid call.
Actual
The action is listed but not found by describe/lookup; exec warns and proceeds.
Impact
Warning noise on a valid call, and entity type parameters of System actions are dropped; usability.
Activity
github-actions commentedon Oct 12, 2026
Issue Triage
Summary:
The reporter finds that
System.VerifyPasswordappears inlist java actionsbut cannot be described or executed, causing a warning and empty entity‑type parameters.Checklist of required bug‑report information
v0.26.0 (release binary, 2026-10-11)11.13.0(blank app)describereturns “java action not found”;execwarns “could not look up Java action … (entity type params will be empty)”mxcli diag --bundle)Missing information:
Please attach the output of
mxcli diag --bundle(or at least the relevant session log) so we can inspect the internal state that leads to this lookup failure.Once the diagnostic bundle is added, the issue will be complete. Thanks for reporting!
Automated triage via OpenRouter — workflow source
Merge pull request #1146 from ako/fix/1445-system-java-action-lookup
fix: resolve System Java actions by name (#1445)