NgRx Store DevTools action history retention limit

Question

Feature: Action History Retention
NgRx Store DevTools records every dispatched action to enable time‑travel debugging and state inspection. The documentation does not specify an upper bound on the number of actions kept in memory, and the default appears to be unlimited. This can lead to significant memory growth in applications that dispatch thousands of actions over time.
Developers working with long‑running or high‑frequency action streams are uncertain whether an internal limit exists, and if so, how it is enforced. The absence of a documented configuration option creates ambiguity when planning for performance and memory usage during debugging sessions.
Key uncertainties:

What is the default maximum number of actions retained by NgRx Store DevTools?
Is there a public configuration API to set or override this limit?
How does the retention policy impact debugging performance in large applications?

Tasadduq Burney · Answer

NgRx Store DevTools Action History Retention
The default maximum number of actions retained by NgRx Store DevTools is 10. This limit is controlled by the maxAge option of the DevTools instrument.

Import StoreDevtoolsModule from @ngrx/store-devtools in your AppModule.
Call instrument({ maxAge: , ... }) inside the imports array.
If you omit maxAge, the default of 10 actions is applied.
After configuring, open the Redux DevTools tab, dispatch more actions than the limit, and verify that the oldest actions disappear from the history list.

The limit only affects the DevTools panel; the NgRx store continues to process every action and update state regardless of the history size. Raising maxAge increases memory usage in the DevTools UI and may slow the panel when actions contain large payloads; lowering it reduces memory usage but may discard actions needed to reproduce complex bugs.

NgRx Store DevTools action history retention limit

Feature: Action History Retention

1 answer

NgRx Store DevTools Action History Retention

Your perspective belongs here.

1 question comment