Conditional premoves not working in correspondence

Conditional premoves are not working correctly in correspondence. I am able to create a conditional premove as normal and save it to be played, but after saving and returning to the game, the move is erased. It is not saved or listed if the analysis board is reopened immediately, and the move will not be played even if the condition is met. I have tried in multiple different games (and tried repeatedly inputting the same move) over the last few days (I think I first noticed about a week ago). I am familiar with the process and this is not a user error.
What’s the dealio?

I’ve also noticed this. Commenting for more attention

Same thing happens to me!

Thanks for the report, we’re looking into it!

Me too, but with a twist.

On the desktop, I can add premoves and they remain in place. Also, when I switch to the app (Android, v8.0.0) those moves are still remembered. All good so far.

But, any moves I add via the app are _not_ remembered

Can someone post a link to a game for which you're unable to create premoves?

I can't seem to reproduce it. If anyone using Firefox or Chrome would like to help us make headway on this, here's what you can do. Go to developer tools (ctrl-shift-i), console tab, click the upper right gear menu, and select "Persist Logs". Then go about reproducing the premove failure in the tab you launched dev tools from. Finally, return to the dev tools console tab, copy all of the contents (the text field beginning with "Lichess is open source! blah blah") and paste then here in this thread.

I can try. i have old version of chrome.. could be a long shot data point.. sorry i can't use more recent versions, programmed obsolescence and all... :) I am soon going to fade out of reality from that, I think.

persists log...
reproduce premove failure (to? transmit to server?)
dev tools console should be filled with info doing the previous step, copy that console log.
and paste here..

How can i make sure it was a failure.. reproducing the op. first. otherwise no pasting if no failure?

We also have local persistence of explored variations.. Sending some of them to premove, does not erase that (thank lichess for that, again). Can serve as log of the reproduced experiment. There it is, there it isn't and look still in the tree. So reload is the test to reproduce op or not.

off-help-desk topic:
I always thought the premove mechanism should be generally more persistent, even after the moves are being conditionally processed, for post-game analysis, to review that aspect of in-game thinking.. That would mean server persistence, and history keeping. I guess the local solution in the user tree, is a safety net for the premoves, for my concern of post-game in-game thinking tracking.

did you mean check "preserve log" in the settings?

upon reload I still see my condition premove.. maybe i kill the tab and go back to game.. nonetheless here is the console log. also I had sent my move, and then added the conditional premove (from the persitent local user tree. so i could repeat this, while opponent is thinking).

Edit: i did not kill the tab but went back to rounds page.. microscope indicate a premove in store.
same thing if i kill the tab. and open a new one from the lobby and then go into the game still there.
But I am not using most recent chrome version. ping me for follow-up in case i did not understand the op.

lichess.min.js:37 Lichess is open source! lichess.org/source
10:32:00.324 analysisBoard.min.js:1 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See www.chromestatus.com/feature/5745543795965952
Ea @ analysisBoard.min.js:1
insert @ analysisBoard.min.js:36
(anonymous) @ analysisBoard.min.js:1
(anonymous) @ analysisBoard.min.js:42
n @ analysisBoard.min.js:1
t @ analysisBoard.min.js:1
(anonymous) @ analysisBoard.min.js:1
10:32:00.328 analysisBoard.min.js:1 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See www.chromestatus.com/feature/5745543795965952
Ea @ analysisBoard.min.js:1
insert @ analysisBoard.min.js:36
(anonymous) @ analysisBoard.min.js:1
(anonymous) @ analysisBoard.min.js:42
n @ analysisBoard.min.js:1
t @ analysisBoard.min.js:1
(anonymous) @ analysisBoard.min.js:1