Executor timeout is hard-coded for long-running project operations

[hjotha]

Problem:

The executor has a fixed per-statement timeout. Large projects and long-running audit operations can legitimately exceed the default, forcing users to fork mxcli or avoid the operation.

Expected:

Operators should be able to increase the executor timeout without changing code.

Impact:

Large project audit workflows are fragile and can time out before producing useful diagnostics.

Proposed fix:

Add an environment variable override for the executor timeout while preserving the existing default behavior.

[github-actions]

Issue Triage

Summary:
The issue requests a way to override the executor’s fixed timeout (e.g., via an environment variable) so long‑running audit operations on large Mendix projects don’t time out.

Checklist for feature request

Required info	Present?	Details
Use case – why the feature is needed / problem it solves	✅	Described: large project audit workflows exceed the default timeout.
Proposed syntax or behavior (if applicable)	❌	Mentions an environment variable override but does not specify the variable name or exact behavior.
Mendix version relevance (if version‑specific)	❌	No mention of which Mendix versions are affected or whether the change applies universally.

What’s missing / polite request

Could you please add:

1. The exact environment variable name you propose (and its expected format, e.g., MXCLI_EXECUTOR_TIMEOUT_SECONDS=300).
2. Whether this change is relevant to all Mendix versions or only specific ones (e.g., 9.x, 10.x).

Once those details are included, the request will be complete. Thanks for contributing!

---

Automated triage via OpenRouter — workflow source