All the operations executed from the UI are being accumulated in a session's registry, this way the user is able to undo/redo.
The issue is that actually the registry implementation is just based on a stack with a given maximum capacity, which results on an exception being thrown once the user exceeds the stack size (see attached screenshot).
The solution for this would imply re-implementing the registry with some evict or rotation policy, avoiding this way get to the limits and just fail with an exception.