Hello,

I am not sure I understand you because what you describe sounds as intentional behaviour.
Conversations "live" within HTTP session. If you end the session (by timeout in this case), then you also end all the conversations.

In your reproducer, the page1 is already linked with a conversation and when you click to page2 you try to propagate it, but after session timeout, that conversation no longer exists. That seems like a valid behaviour to me.

Since you didn't provide sources but only WAR, I am not sure you are attempt to use conversationPropagation=none but the deployed application apparently attempts to propagate the long running conversation as I can see cid=x as part of the URL.