Got a workaround for this.
Thank you for the quick update.
Here I would definitely ask if you use the persistentState.