Runtime Errors

Diagnose application startup and action failures

Capture the failing operation, exact artifact version, and the first relevant exception with its cause. Check the assembled QInstance with QInstanceValidator. Missing named backends, tables, processes, or code-reference classes are configuration or packaging issues that should be fixed before serving traffic.

Compare the packaged JAR and environment with the working development setup. Verify the server entry point and scheduler startup. For an action failure, inspect its typed output and record errors as well as the log. Report a minimal reproduction through GitHub issues, with credentials and application data removed.