Gary~

Unfortunately, it does not seem like they know what is going on. They are currently analyzing logs of what’s happening when the error occurs. Hoping to hear more details soon …

Sorry I don’t really have any more info than that to share at the moment … 
Karen 

Tanzir, this behavior is expected with Page Caching. Page Caching is recommended for users building Skuid Pages that are shown on Force.com Sites, where there is no authentication involved, but it is currently not recommended to use Page Caching within an authenticated environment (e.g. anywhere other than on Force.com Sites) because the entire you will have stale session information cached. 

The behavior is NOT expected when Page Caching is disabled, and we are continuing to investigate on our own as well as in conjunction with Salesforce Support.

Hi Gang~

I know you are all anxiously awaiting updates about this issue. Unfortunately, still no updates from the Salesforce end but we wanted to assure you that our devs are actively working on a resolution for this as well. Hope to have good news to share with you soon. 

Thanks again for your patience!!!
Karen 

Our community users have also experienced this issue. I know we are waiting on Salesforce to come back with an answer, but has anyone found a work around until they find the issue? This is causing our sales team to have major issues during the sales process.  

Also one thing that we have noticed is that if you switch tabs in our browser and then come back it ask us to sign back in we currently using chrome as our browser.

Thanks for any help that someone may give.
Sierra

This really is becoming a major issue. When working on editing Skuid pages all day, it is happening to me very often, and I lose all of the changes I’m trying to make each time.

We are almost ready to release a new version that includes a fix for this issue — the fix should be available by Monday. 

Zach, Really appreciate Skuid taking the lead on this fix. Best regards, Bill

Us too

Hi Zach, are you guys rolling out the fix or is it something we need to download?

Looks like they rolled it out in the 8.15.7 iteration: https://www.skuid.com/skuidreleases

Hi beloved community~

Thank you all so very much for your patience and assistance over the past month plus as we worked with Salesforce to resolve this issue. John is right that this issue has now been resolved in Rockaway Point Release - Iteration 9 and is now available from the Skuid Releases page at http://www.skuid.com/skuidreleases.

We wanted to give a little more detail than just a “it’s been fixed” update. It took us a while to find the solution because the issue was so difficult to pin down and reproduce, as many of you can attest to with its inconsistent behavior. The final solution is based on this knowledge base article Ben found which, while it’s not immediately apparent that the issue from the article was what we were experiencing, should do the trick. We are still trying to figure out with Salesforce why the sessions and CSRF tokens were becoming invalid in the first place. 

Thanks again for your patience and understanding during this process! Please let us know if you have any continued problems with this after upgrading.

Thanks!
Karen