Runtime Status Errors and Limits Reference

English | 简体中文

Applies to DecisioWorks v1.4.0. Runtime license information remains authoritative.

Runtime status, error codes, and resource limits

Action status

Status	Meaning	Next step
ok	Action completed	Review output and evidence
skipped	Optional condition not configured	Confirm whether the step is required
failed	Controlled action failure	Diagnose by action, code, and diagnostic ID
Waiting	Stage not submitted	Complete prerequisites
No feasible solution found	Search has not obtained a feasible candidate, possibly because time expired	Inspect the solver status and stopping reason; this is not an infeasibility proof
Proven infeasible	The solver proved that the current model and inputs cannot satisfy the hard constraints	Review conflicting data and constraints before rerunning
Time limit reached	Solving ended at its limit	Check whether a feasible incumbent exists

These solver descriptions explain results; they do not introduce new API status values. An action returning ok has completed. Inspect the solver status and result records to determine feasibility and optimality.

Public runtime error codes

Public error code	Meaning	Recommended action
RUNTIME_LICENSE_MISSING	No valid commercial license found	Check license.rkey location and permissions
RUNTIME_LICENSE_EXPIRED	License expired	Request and install a renewed license
RUNTIME_LICENSE_HARDWARE_MISMATCH	License does not match this device	Generate a request on the target device
RUNTIME_PACKAGE_MISMATCH	Package and authorization do not match	Verify release/license pairing
RUNTIME_SIGNATURE_INVALID	Signature validation failed	Use the original issuer file without repacking
RUNTIME_UNAUTHORIZED	Requested scope is not authorized	Check license level and scope
RUNTIME_IMPORT_FAILED	Controlled runtime failed to load	Check package, platform, Python, and dependencies
RUNTIME_RESPONSE_INVALID	Runtime returned an unrecognized result	Retain the diagnostic ID and contact support
RUNTIME_EXECUTION_FAILED	Execution did not complete normally	Review authorization and scenario configuration

Public responses should contain a stable code, user guidance, and a diagnostic ID, not a full stack trace, absolute path, or license internals.

Current resource policy

Edition/level	Maximum solve time	Maximum threads
Research	300 seconds	10
Commercial Basic	1,800 seconds	8
Commercial Professional	1,800 seconds	8
Commercial Enterprise	7,200 seconds	32
Commercial Platform	Per platform authorization	Per platform authorization

The Web cockpit should derive control ranges from runtime policy and validate requests before submission. Recipe values are requests and cannot exceed the active authorization.

Diagnostic Order

1. Check readiness for the selected dataset and capability.
2. Check authorization, release, platform, and Python compatibility.
3. Keep requested threads and time within the displayed limits.
4. Distinguish data, configuration, and authorization failures from no candidate found, proven infeasibility, and a time limit reached with or without a feasible candidate.
5. Retain the version, dataset ID, action stage, error code, timestamp, and diagnostic ID.

For public support requests, provide the error code, diagnostic ID, version, reproduction steps, and necessary redacted logs. Supply authorization-verification material as requested by support.