I have a menu tree component in my application. When the application is freshly opened, on clicking the menu items, navigation happens correctly. From what we’ve observed, after a while, the menu tree no longer navigates to any page and the application has to be reloaded, for it to work again. Any possible solution for this?
Does it take a consistent amount of time for the navigation to fail? (1 hour? 2 hours?) Does it appear to be tied to navigating to specific views? When clicking an item in the menu for navigation, is the URL in the browser address bar actually changing or is it remaining the same (this might vary depending on the navigation method). Are there any errors in the browser console? (F12 in the browser on nav fail)
What I would do, is add a logger to your menu tree component, where it logs a value on click. I would be curious whether the clicks stop ‘functioning’, whether the menu tree doesn’t process them, or something else is occurring.
Do you have to log in for your application, and you have an automatic log-out set up after a certain time of inactivity?
Sounds like the client is locking up to me. Is it just the tree that's affected? Can you interact with the rest of the page at all? Popups open, values updating ok, etc? If not, then then you've most likely got something that's building up memory until it eventually runs out.