When testing, I've found it helpful to log off and start with a fresh session one last time before implementing new code. Every once in a while, I'll catch a mistake where the code was only working because of some previous iteration of execution.
For me, it has unfortunately been more often than "Every once in a while", but in SAS Studio the problem has always been fixed by restarting the session using the SAS Studio menu option. That's easier and faster than logging out and back in. There may be a circumstance when that doesn't suffice, but I haven't found it yet (other than the case where there's a Windows memory leak somewhere - SAS Studio or the browser - and I have to not only log out but also close and restart the browser).
... View more