No flow execution could be found with key 'e54s1'

Cantor, Scott cantor.2 at
Wed Nov 28 10:50:56 EST 2018

That's probably a SSO redirection loop, combined with cookie(s) not reaching the server properly, resulting in each request dying mid-stream when it can't get at the original servlet session to locate the flow conversation matching the parameter, and then somehow it's repeating because of the loop. Logging can track the container session ID and correlate all of this to missing cookies causing new JSESSIONID values, or load balancer issues when multiple servers are involved.

All of these problems are back button, bookmark, timeout, or cookies. That’s it, that's really all there is 99% of the time. The causes are environmental (load balancers, user behavior, browsers breaking, a million other things) and are basically in the member support bucket for me now because it's so time consuming to track down or even help somebody track it down.

-- Scott

More information about the users mailing list