
4 件の回答

We finally got the issue resolved by identifying an APEX Class that required us to bring the API level up to at least V.29 (we brought it up to V.40). Salesforce R&D got involved to help our partner identify the class. You might be able to identify the class by first running "Compile All Classes" under APEX Classes and then reviewing the list of classes - look for anything that does not have the "Is Valid" indicator checked.