They do, but pause works a little differently.
Since you can’t send non-realtime commands in a hold state, pause automations have the following effect:
- Stop sending on the sender side (workflow pause)
- Empty buffer (firmware handles all planned movements)
- On empty buffer, send pause automation - so the pause code will actually run
- Actually hold the firmware using !
The side effect of this is that pauses are no longer instant (as if we held instantly we’d have no way to send the pause automation code)
The issue that OP might be seeing is hitting pause and not seeing anything happen - because planned movements need to finish before the automation is sent.