a redo was refused by a before-event handler...

Warnings reference › kanban:redo:vetoed

Identifier

kanban:redo:vetoed

Raised by

Kanban

Since

1.95.0

What happened

A redo re-runs the change through the board's own write path, and a beforeMove/beforeEdit handler (or the WIP gate) refused it on the way back in. The card stayed where it was and the redo step was not consumed, so the history is exactly as before the attempt.

The fix

Remove or relax the vetoing handler for that card, or re-apply the change manually once the gate would let it through.

The smallest fix

board.on('beforeMove', (ev) => { if (ev.to === 'done') ev.preventDefault('done is closed'); });

Reference

Covered in full at the API reference.