Stack Depth Limits

Stack Size Configuration

// historyMiddleware.ts
export const HISTORY_STACK_SIZE = 50; // configurable at build time

// Applied when pushing to the undo stack:
const newUndoStack = [snapshot, ...undoStack].slice(0, HISTORY_STACK_SIZE);

// When the stack reaches 50:
// Entry 51 causes entry 1 (oldest) to drop off the end
// Users cannot undo beyond 50 actions

Memory Implications

Adjusting Stack Size

// For memory-constrained environments or very large workflows:
// Reduce HISTORY_STACK_SIZE in historyMiddleware.ts

// For power users working on complex designs who need more history:
// Increase HISTORY_STACK_SIZE (be aware of memory usage)

// There is no runtime API to change stack size — it is a build-time constant
// A future enhancement could make it a user preference (stored in tenant settings)

History is Session-Only

The undo/redo stacks exist only in memory for the current browser session. Refreshing the page clears all history — the workflow loads from the server at the last saved state. This is intentional: cross-session history would require significant server-side storage and adds complexity around merge conflicts.