Script settings
The Scripts page holds the settings that control how actions run, whatever they are written in (Steps, Script or AutoHotkey). Changes take effect when you choose Apply or Save and close.
note
Advanced mode. The whole Scripts page is hidden in Simple mode; it is in the Engine section of the navigation. The settings keep working in Simple mode with whatever values they have.
For how actions run in general — one thread each, what stops them, what a failing step does — see How scripts run. The AutoHotkey switch and program are on the General page.
AUTOMATION
Actions
Text expansion
Snippets
Recorder
Sandbox
App groups
Ignore groups
Gestures
ENGINE
Global events
Exclusion zones
Scripts
Plugins
SETUP
General
Appearance
Profiles
Console
Security
Help
About
Scripts
Timeouts, limits and behavior for running actions and scripts.
Limits and timeouts
Before and after timeout
3000ms
Maximum running actions
50
Behavior
Typing delay
30ms
Limits and timeouts
| Setting | What it does | Default | Range |
|---|---|---|---|
| Before and after timeout | How long each Before or After script may run (Before and after actions). One still running after this is stopped and the next step starts; the stop is written to the console's System section, with no prompt. The matched action itself is never cut short. At 0, each Before or After script gets one very short wait before it is stopped. | 3000 ms | 0–60000 ms |
| Start and shutdown wait — Started, Shutting down | How long the Config loaded event (when Input.Observer starts) and the Engine shutting down event can run before you are asked whether to keep waiting (Global events). Input.Observer never stops them on its own: if you choose to keep waiting, it asks again after the same time. When a save or Reload Config runs Config loaded again, there is no time limit and no prompt. At 0 you are asked at once. | 10000 ms each | 0–600000 ms each |
| Maximum running actions | A safety limit on how many actions and scripts run at the same time. Reaching it does what the stop-all hotkey does: every running action stops, and gestures and other input handling stay off until you choose Reload Config from the tray menu. It protects against an action that keeps starting itself. | 50 | 1–10000 |
| Maximum time scripts can block input | The longest EngineConsumePhysicalInput or a replay of a temporary macro recording can keep your own mouse and keyboard input from reaching other programs. A longer request is shortened to this. | 120 s | 1–86400 s |
| Plugin command queue size | How many PluginSendMessage calls can wait for one plugin at a time. One more is refused, which stops the script that made it with an error. 0 queues none: a call made while another is waiting for the same plugin is refused. | 10 | 0–1000 |
Behavior
| Setting | What it does | Default | Range |
|---|---|---|---|
| Typing delay | The pause between characters when an action types text, and between the keystrokes of a text expansion. Some programs, such as Notepad on Windows 11, scramble text typed with no pause. 0 sends the characters back to back. | 30 ms | 0–1000 ms |
| Send media and browser keys as commands | Sends the media, volume and browser keys (play, next track, volume up, browser back and so on) to the control that last had the keyboard focus as commands, instead of as keystrokes. Some controls respond to these keys only that way. Every other key is sent as a keystroke either way. | Off | On or off |
| Allow bringing windows to the front | Lets Input.Observer turn off Windows' delay that stops programs from taking the focus, once, when it starts, so its actions can bring windows to the front immediately. Off, Windows may only flash a window's taskbar button instead of activating it. This setting applies to your whole Windows session, not only to Input.Observer. | On | On or off |