Starting November 20, the site will be set to read-only.
On December 4, 2023,
Apex Code Development (90768)
General Development (55146)
Visualforce Development (37251)
Lightning (18265)
APIs and Integration (17146)
Trailhead (11680)
Formulas & Validation Rules Discussion (11337)
Other Salesforce Applications (8116)
Jobs Board (6655)
Force.com Sites & Site.com (4842)
Mobile (2694)
You need to sign in to do that
Don't have an account?
In my production instance, when I updated a utility class that a number of other classes depend on, I saw that these other classes were then marked "IsValid" = unchecked, and they had no wsdl link, in Setup/Develop/Classes.
After performing "Run All Tests", they were marked valid.
What is going on here?
This happens whenever you have dependent metadata recompiled and the code is marked as Not Valid because it wants you to recompile to ensure everything still meshes. For example, you might change a signature of a method and now the dependent class won't work when accessed any longer. By running the tests, that's one way to get all of the classes to recompile.