Both the Alexa dev console and the ASK Lambda console time out unused sessions -- which is good -- but do not provide any visual indication that this has happened. At least one of these consoles (I don't remember which) compounds that problem by then responding to user requests with 401 errors rather than explaining that the user needs to sign in again.

The better response would be to handle this by popping up a message that the session has timed out and the user needs to log in again.

The best response would be if that popped-up message included the user and password fields, so we could fix the problem right there, without changing the console window's state otherwise. I've found that I can maintain state by using "open in another window" to a link which will cause the login to occur, but the user shouldn't have to guess at server/browser behaviors to achieve that.