Ensure that the FlushOnResponseCommit setting is set to true for the GAE SessionCaches.
This configuration was suggested by @janbartel.
If true, a dirty session will be written to the SessionDataStore just before a response is returned to the client. This ensures that subsequent requests to either the same node or a different node see the changed session data.
I redeployed the QA probers for all runtimes, and it seems OK now.
Still not 100% sure this is it because it used to work before, but QA is green with this and the sessions test.
Thanks!
Ensure that the
FlushOnResponseCommit
setting is set totrue
for the GAESessionCache
s. This configuration was suggested by @janbartel.