Installation

Keybind is set but nothing fires

First, update GRIP-EMS through your addon manager. As of v2.3.14, Key Down Casting is forced on automatically and this is no longer something you can misconfigure. If you are still on an older version, run /gems settings, go to the Cvar Health tab, and click Fix if the row is not green; this solves the majority of pre-2.3.14 keybind problems. On 2.3.14 or later, if the sequence still does not fire, check that you have a target selected and that the sequence has a keybind assigned in the Keybinds tab inside the editor, not just in WoW's default keybind menu.

I put a sequence's macro on my action bar and pressing it does nothing

Multi-version sequences generate a macro you can place on a bar, but clicking that macro with your mouse or pressing it from an action bar slot is not the same as a Keybinds-tab bind, and it will not fire the sequence correctly on its own. GRIP-EMS is built around binding a key directly to the sequence inside the editor's Keybinds tab, not around action bar buttons. If you want the drag-and-drop, click-to-fire workflow you may be used to from the legacy program, install Daxomault's GRIP-EMS Actionbutton Override addon, which adds that behavior back as an option.

Sequence fires once then stops

GRIP-EMS requires continuous repeated keypresses, not a single press and hold. Your hardware or software needs to be configured to send repeated keypress events. At 150ms that is roughly 6 to 7 presses per second. A single press fires one step and stops.

Sequence shows greyed out after a /reload in arena or M+

This was a known bug where the addon waited on a match flag that never cleared mid-fight, leaving sequences inactive until the match ended. Update GRIP-EMS through your addon manager. Clicking a greyed-out sequence row in the editor also re-activates it on the spot.

Sequence key stops working randomly while grinding, mount and dismount fixes it

This was a bug where the addon waited on a match-privacy flag that never cleared outside of arena or Mythic+ specifically, which could leave a sequence marked dormant longer than it should have been in some overland situations. Update GRIP-EMS through your addon manager. Clicking the greyed-out sequence row in the editor re-activates it immediately without needing to relog.

Sequence key dies after skyriding or leaving a vehicle

The keybind suspend-and-restore runs inside the secure engine and survives skyriding, vehicle exits, and possession. If you are hitting this, update GRIP-EMS through your addon manager. You can also press your sequence key while skyriding over an attackable target and it will dismount and fire step 1 in a single press.

Sequence key fires mid-air or vehicle keys are dead on first flight of the session

This has been reported as a first-takeoff issue where ground binds stay live while airborne or vehicle keys never activate. It has not been independently confirmed as fixed in a specific release the way the other keybind issues on this page have been. If you hit this, update GRIP-EMS to the latest version first, and if it persists, report it in the Discord with your GRIP-EMS version and whether it happens on every login or only occasionally.

Another addon keeps stealing my sequence keybinds

Some addons override-bind the same keys GRIP-EMS uses for vehicles and skyriding, and whoever loads last wins. The Keybinds tab inside the editor names the contending keys directly in the vehicle and pet battle sections so you can see exactly which addon is causing the conflict. GRIP-EMS does not fight for the bind, it just tells you who took it.

Sequence says a spell cannot be found, but it works fine once I am in the right form or proc

This is expected behavior, not a bug. GRIP-EMS checks whether a spell is castable right now before it will queue it in a step. Some spells only exist, or only become the correct version, in a specific state, such as Void Volley replacing Void Bolt only while a Shadow Priest is in Voidform, or a spec-specific proc swapping what a button actually casts. Outside that state the addon correctly reports it cannot find the spell, then the step behaves normally the moment you are actually in the state where the spell exists. If the step is working in practice once the condition is met, there is nothing to fix. If you want the warning to stop appearing while testing outside the triggering state, an addon like ErrorMonster can redirect the message so it does not clutter your chat window.