--- schema_version: "1" id: eb0c969c51c1a079d7590f3b4f24a8ab4f7628951f52ecbcdd2debec7b2e2c1c title: ApexSettings collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_apexsettings.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_apexsettings.htm source_site: developer.salesforce.com content_type: documentation content_hash: a8e04859f6bdcc8b1637919362de90264e99c05028ba86f529befd2f94155a5b description: Represents Apex-related org settings. This type extends the Metadata metadata type and inherits its fullName field. --- # ApexSettings Represents Apex-related org settings. This type extends the Metadata metadata type and inherits its fullName field. In the package manifest, all organization settings metadata types are accessed using the Settings name. See [Settings](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type.") for details. ## File Suffix and Directory Location ApexSettings values are stored in the Apex.settings file in the settings directory of the corresponding package directory. The .settings files are different from other named components, because there’s only one settings file for each settings component. ## Version ApexSettings components are available in API version 47.0 and later. ## Fields

Field Name	Field Type	Description
asyncApexExecutionsOverride	integer	Use this field to specify an override value that is less than the licensed rolling 24-hour asynchronous Apex job limit. The org defaults to the licensed asynchronous limit if the override is `0`, `null`, or omitted. Applicable to only nonproduction orgs, including sandboxes, scratch orgs, and Developer Edition orgs. Used for testing elastic processing behavior. See Elastic Limits for Asynchronous Apex Jobs (Beta). Available in API version 68.0 and later.
DefaultQueueableDelay	integer	Indicates the admin-controlled minimum delay (in seconds) that applies to all enqueued jobs that were scheduled without a delay parameter. The minimum delay is one second and the maximum is 600 seconds. The default behavior, when the setting is omitted, is no delay in scheduling enqueued jobs.
enableAggregateCodeCoverageOnly	boolean	Indicates whether aggregate (not detailed) totals are tracked for Apex test coverage data (`true`) or not (`false`). The default value is `false`.
enableApexAccessRightsPref	boolean	Deprecated.
enableApexApprovalLockUnlock	boolean	Indicates whether approval process lock and unlock operations from Apex code are allowed (`true`) or not (`false`). The default value is `false`.
enableApexCtrlImplicitWithSharingPref	boolean	Indicates whether the Use `with sharing` for `@AuraEnabled` Apex Controllers with Implicit Sharing critical update is activated (`true`) or not (`false`). For more details, see the Winter ’20 Release Notes.
enableApexPropertyGetterPref	boolean	Indicates whether the Enforce Access Modifiers on Apex Properties in Lightning Component Markup critical update is activated (`true`) or not (`false`). For more details, see the Winter ’20 Release Notes.
enableAsyncApexElasticExecutions	boolean	Indicates whether the Use elastic limits for asynchronous Apex jobs (Beta) setting is enabled (`true`) or not (`false`). The default value is `false`. Available in API version 67.0 and later.
enableAuraApexCtrlAuthUserAccessCheckPref	boolean	Indicates whether the Restrict Access to `@AuraEnabled` Apex Methods for Authenticated Users Based on User Profile critical update is activated (`true`) or not (`false`). For more details, see the Winter ’20 Release Notes.
enableAuraApexCtrlGuestUserAccessCheckPref	boolean	Indicates whether the Restrict Access to `@AuraEnabled` Apex Methods for Guest and Portal Users Based on User Profile critical update is activated (`true`) or not (`false`). For more details, see the Winter ’20 Release Notes.
enableBlockPackagedApexExecAnon	boolean	Indicates whether the Block Apex Anonymous Code Execution from Managed Packages release update is enabled (`true`) or not (`false`). The default value is `false`. Available in API version 67.0 and later.
enableCompileOnDeploy	boolean	Indicates whether Apex code is automatically recompiled (`true`) or not (`false`). When set to `true`, code is recompiled before completing a metadata deployment, change set deployment, package installation, or package upgrade. For production orgs and full sandboxes, the default value is `true`. For all other orgs, the default value is `false`. Note This setting can’t be disabled in production orgs.
enableDisableParallelApexTesting	boolean	Indicates whether Apex tests are serially executed (`true`) or not (`false`). The default value is `false`. Note Even when parallel testing is enabled by setting this value to `false`, tests that are run during deployments are always run serially.
enableDebugLogsDuringDeployment	boolean	Indicates whether debug logs are enabled during metadata deployment (`true`) or not (`false`), in conjunction with an active debug log trace flag. If this setting is `true` but the trace flag is not active, debug logs are not enabled during metadata deployment. The default value is `false`. Note Enabling the debug log in the `DebuggingHeader` overrides this setting.
enableEnforceSummer26ApexHeapLimit	boolean	Indicates whether a nonproduction org is restricted to the lower Summer ’26 Apex heap limits (`true`) or not (`false`). The default value is `false`. This setting is available only in Winter ’27. In Spring ’27, the higher Apex heap limits are enforced globally regardless of the setting status. For more details, see Handle Larger Datasets with Increased Apex Heap Limits. Available in API version 68.0.
enableGaplessTestAutoNum	boolean	Indicates whether autonumbering gaps are prevented by Apex test executions not incrementing autonumber fields for non-test records (`true`) or not (`false`). The default value is `true`.
enableMngdCtrlActionAccessPref	boolean	Indicates whether the Disable Access to Non-global Apex Controller Methods in Managed Packages critical update is activated (`true`) or not (`false`). For more details, see the Winter ’20 Release Notes.
enableNonCertifiedApexMdCrud	boolean	Indicates whether Apex classes can access metadata, public or protected, through classes in the `Metadata` namespace (`true`) or not (`false`). The default value is `false`.
enableRestrictCommunityExecAnon	boolean	Indicates whether guest users are restricted from executing anonymous Apex. The restriction applies regardless of whether the `Author Apex` permission is set. The default value is `true`.
enableSecureNoArgConstructorPref	boolean	Not used. Critical update is automatically enforced. See Restrict Reflective Access to Non-Global Constructors in Packages (Critical Update).
enableTestSetupSkipTestResults	boolean	Indicates whether Apex test results are generated for @TestSetup methods (`false`) or not (`true`). Available in API version 61.0 and later.

## Declarative Metadata Sample Definition The following is an example of ApexSettings components. true The following is an example package.xml manifest that references the previous definition. Apex Settings 47.0 ## Wildcard Support in the Manifest File The wildcard character \* (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see [Settings](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/meta_settings.htm). For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).

Note

Note

Note