On 6 Dec 2025, at 3:38 am, Samuel Pelletier <[email protected]> wrote:
> The page restoration error is more complex to handle. Page restoration occurs > with component actions (action bindings) that use the WO auto-magic context > restoration that make our job easier. This magic is based on the session > pageCache, if the request comes from a page no longer there, it fail with the > page restoration error. > > Usually, I set the page ca size very low (2-5) so opening tab almost always > trigger this error when the user try to use the original one. You have some > choices to eliminate or reduce this error: > > 1- Raise the cache size in the application constructor with > setPageCacheSize(20); You specify the number of pages to keep. This will > raise the memory requirement of your app with all those page states and your > user will almost certainly always find a way to go over the limit. Thanks Samuel—this is a fix. I was running this at 5, and bumping it to 7 was enough to fix the issue. Interestingly, it wasn't reproducible across all apps—I have another example where 5 is sufficient. Anyway, I am happy to back away slowly. -- Paul Hoadley https://logicsquad.net/ https://www.linkedin.com/company/logic-squad/
