I wonder if this is related to the static resource issue that we’re experiencing, as detailed here: https://community.skuid.com/t/skuidified-site-page-404-error-on-static-resources?topic-re…

What happens if you remove the “skuidreloadcount=1” parameter from the URL?

It briefly loads a blank page then refreshes with the parameter in place. In fact, when the page first loads, the behavior is the same. The initial load is without the parameter, then it quickly reloads with the parameter. I assume Skuid is catching the error, retrying once, then giving up.

Still stuck at a blank page. Anybody have any ideas?

Have you granted login access to Skuid Support?

Skuid support has 3 days’ access to our sandbox named UATQA18. Let me know if you need more details.

Peter, do you know if is this happening in other Sandboxes as well? Particularly Sandboxes on other instances than CS79?

After review, this appears to be a significant issue with Salesforce Static Resources that is very similar to an issue we experienced several years ago. We are reporting this to Salesforce Support and will keep you updated.

Peter, can you please Grant Login Access to Salesforce Support for that time frame as well? Thank you!

Peter, while there is certainly a Salesforce issue going on here, one course of action would be to install the latest patch of the Skuid Rockaway release into your Sandbox, to see if that resolves the issue. If it does not, we will be dependent on Salesforce to resolve, but if it does resolve the issue, you will be unblocked. Here is the link to the last patch release of Rockaway: 

https://skuid.secure.force.com/Releases?platform=Salesforce#a0d4000000HefYAAAZ

Zach, I’ve granted Salesforce support 3 days’ access to the Sandbox. We’ve created many sandboxes recently as part of a major development effort that ended in early January and have never seen this problem before.

However, I just checked a developer sandbox that was created in the last week, and it also has a Skuid problem. When I click the tab to bring me to the Skuid page listing, I see the following message.

An internal server error has occurredAn error has occurred while processing your request. The salesforce.com support team has been notified of the problem. If you believe you have additional information that may be of help in reproducing or correcting the error, please contact Salesforce Support. Please indicate the URL of the page you were requesting, any error id shown on this page as well as any other related information. We apologize for the inconvenience. 
Thank you again for your patience and assistance. And thanks for using salesforce.com! 
Error ID: 1135227918-38730 (-1645026840)

Zach, our production instance is still on Salesforce 8, and we’re in a period of heavy usage. Our current worked is aimed at fixing bugs in production and at building functionality to be used internally immediately after our external users finish providing data to us. Therefore, I assume that updating Skuid on our development sandbox wouldn’t be productive because we would be deploying to the older Skuid version. Do you agree?

Peter, that is true that you would be deploying to the older Skuid version, but we would highly recommend upgrading in one of your Sandboxes for the following reasons:

1. It is a slim possibility that upgrading will cause the “blank” page issue to go away in this Sandbox. Since this Sandbox is currently unusable in its current state, it seems to me that it couldn’t hurt anything. You could always delete this Dev Sandbox and recreate.
2. If you are going to be remaining on the Rockaway release, as opposed to upgrading to Brooklyn or Millau, we would highly recommend that you be on the latest Rockaway patch release — you are about 5 patches behind on Rockaway.

Peter,

This is due to a known issue with Spring 18 which Salesforce is in progress of releasing a patch for, as we speak. 

Here is the known issue page:

https://success.salesforce.com/issues_view?id=a1p3A0000018BvQQAU

Please indicate that this issue affects you — once the fix has been released to your affected Sandbox orgs’ instances, you should refresh the Sandbox in order for the fix to be applied.

Regards,

Zach

Zach, I’ve indicated that the issue affects me. My two impacted sandboxes are on CS13 and CS79. The Known Issue page indicates that the fix has been pushed out to both of these servers, but the behaviors are unchanged on both sandboxes (blank page on UATQA18, error message on GR17M19). Is there anything I should have to do in order to see the impact of the fixes? FYI, we have not yet patched Skuid on either sandbox.

Salesforce Support told me that you will need to refresh these sandboxes in order for the fix to take effect.

Zach, the link you provided lists a large number of Skuid versions. If I’m going to patch one of my sandboxes, should I use Rockaway Iteration 15? This appears to be the latest fix to Rockaway.

Peter, yes I would use Rockaway Iteration 15.

I’ve refreshed GR17M19 with no change in behavior. I have a support request in to Salesforce requesting a waiver so that I can refresh UATQA18 ahead of the normal 29-day limit, but I haven’t heard back from them yet.

Peter, do you mind trying again to refresh GR17M19 and letting us know if that fixes the issue? I just want to make sure that there was not a timing issue with their release of the patch happening after you tried to refresh. If that doesn’t work, I will let Salesforce Support know on our end so that they can take another look. Thanks for your patience.

Zach, I’ve re-refreshed GR17M19, and Skuid appears to be working properly. I can bring up the list of pages and bring up a page in Edit view. Now I’m just waiting on a waiver from Salesforce so I can get my full sandbox refreshed and get back to work. Thanks for your help.