Troubleshooting

Record the trigger, expected action, observed result and recent changes. Follow the input-to-command chain one step at a time.

Startup fails

Check the complete runtime directory, writable paths, supported CPU and conf.toml with def and gs sections. Keep the matching AHK_Z build. Save the full error report. The runtime can write err.txt, and removing hide_console=1 exposes the console on restart.

All hotkeys fail

Check that def_hotkey exists and starts automatically. key properties are appended to this host. For a single failed shortcut, check conflicts, hotif, duplicate command names, the extension and restart.

A gesture does nothing

1. Test the action through a known shortcut.
2. Confirm the trigger button and allowed application.
3. Export the log with the starter Ctrl+Alt+F11 command.
4. Check the recognized trajectory and release string.
5. Check scope, conditions and the final selected command.

gs describes recognition, dn/up identify execution stages, and undef/tip can identify unmatched input. Internal timing values need their own units before performance comparisons.

A command runs old code

Restart after changing list code, metadata or preloaded scripts. read is intended for new independent debug instances. Cached pool functions and labels can continue using previously compiled code.

Missing fields or remaining processes

Verify that the trigger supplies the requested context and the target exposes the needed information. Independent e processes can continue after the root exits. Use their own exit action when needed.

When reporting a problem, include the version, command definition, target application, trigger and full relevant error or log. Review private window titles and paths before sharing.