• Patrick Shouse 8
  • NEWBIE
  • 0 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 1
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 2
    Replies
My deployment times to NA33 have increased from 18 minutes to 67+ minutes since the last time I did a deployment two months. The change is largerly due to slow running Apex Tests. The tests themsleves have not changed in any substantial way. Is anyone else having this problem?
We have an App that has a custom tab that is configured to be its default landing tab. Prior to Winter 16, when a user logged in, the custom tab was loaded as expected. Post Winter 16, Salesforce now displays this page:

You will be redirected to https://c.cs23.visual.force.com/apex/TaskList?sfdc.tabName=01r70000000Mb7O.

Click the button below to go to that page.

And the user has to click OK before the expected landing page will load.

This change in behavior seems to be directly related to the upgrade of the sandbox to Winter 16. Has anybody else seen this? How can we fix this? 
We have an App that has a custom tab that is configured to be its default landing tab. Prior to Winter 16, when a user logged in, the custom tab was loaded as expected. Post Winter 16, Salesforce now displays this page:

You will be redirected to https://c.cs23.visual.force.com/apex/TaskList?sfdc.tabName=01r70000000Mb7O.

Click the button below to go to that page.

And the user has to click OK before the expected landing page will load.

This change in behavior seems to be directly related to the upgrade of the sandbox to Winter 16. Has anybody else seen this? How can we fix this? 
We have an App that has a custom tab that is configured to be its default landing tab. Prior to Winter 16, when a user logged in, the custom tab was loaded as expected. Post Winter 16, Salesforce now displays this page:

You will be redirected to https://c.cs23.visual.force.com/apex/TaskList?sfdc.tabName=01r70000000Mb7O.

Click the button below to go to that page.

And the user has to click OK before the expected landing page will load.

This change in behavior seems to be directly related to the upgrade of the sandbox to Winter 16. Has anybody else seen this? How can we fix this?