When does Angular's change detection fail to work properly?

Scenarios where Angular's change detection might not work as expected, specifically in projects and library components.

1. Changes in Asynchronous Operations
   you may need to manually trigger change detection using ChangeDetectorRef.detectChanges()

2. Immutable Objects
   An object where its reference does not change, but its internal state does. You should use methods that return new instances when modifying immutable objects (e.g., Array methods like map, filter, etc., or libraries like Immutable.js, a nested object or array).
   ex.

   this.agGridDynamicConfig = {... this.agGridDynamicConfig}

3. Events Outside Angular's Zone
   If events (like DOM events) occur outside Angular's zone. You can use NgZone.run() to execute code within Angular's zone.

4. Third-Party Libraries
   If you're using third-party libraries that manipulate the DOM directly or change component state outside Angular's knowledge, you may need to wrap these operations in Angular's zone or handle change detection manually