Evil Session State and the stupid "me" got me again

I was working on session state on ASP .NET and I made a stupid mistake of storing an object into session and after it got stored in session some observer (utilizing observer pattern) is updating some data based on statuses and actions. And as lame as I can get I did not realize that the object in session is not in synch with DB data anymore.

Maybe we are using the wrong strategy, I need to go back and revisit the strategy and re-factor the code as needed. For now I'm forcing the object in session to be updated from DB.

Lesson learned: "Use Session State "CAREFULLY" and "SPARINGLY" "; use it only as on a need basis

Give me your thoughts