Salesforce's own documentation states that the Auto-Activation date of Critical Updates is the date they force the update on you, you cannot turn it of, etc etc.
Anyone know the reality of this?
In 4 years, I've yet to see any consistency on this. I have two past-due updates they're not forcing on me yet.
- Serve Static Resources from the Visualforce Domain
- Auto-Activation: 12/10/2014 - 0 days remaining
- Enable governor limits on all executed flows
- Auto-Activation: 1/11/2015 - 0 days remaining
Update 2015-02-03 from SF Support: I heard back from some of my colleagues on other skill group teams. With regards to the Enable Governor Limits, we are going to create a separate case with our Config team to take this up with Tier 3 / R&D to investigate see if they can determine why this particular critical update did not take place as scheduled. They may also have more for you in terms of messaging as to why they remain in the list and the due date does not update. (my translation - left hand, right hand, no clue right now) :-)