The AdditionalFieldHistory scratch org feature is capped at a maximum value of 40 (yielding 60 total tracked fields when combined with the base 20). This limit does not reflect the current platform capability: as of Spring '26 (API v66.0), Field Audit Trail supports up to 200 tracked fields per object. The feature cap should be raised to 180 to match (20 base + 180 additional = 200).
Steps To Reproduce
Create a scratch org definition file with AdditionalFieldHistory set to a value greater than 40, e.g.:
json{
"edition": "Enterprise",
"features": ["AdditionalFieldHistory:100"]
}
Run sf org create scratch -f
Expected result
Scratch org is created with support for up to 200 tracked fields per object, consistent with the Field Audit Trail limit introduced in Spring '26.
Actual result
INVALID_INPUT: 100 is not a valid quantity for the Features value AdditionalFieldHistory.
Scratch org creation fails. The maximum accepted value is 40.
Additional information
The Field Audit Trail documentation (help.salesforce.com) now states a limit of 200 tracked fields per object for orgs with Salesforce Shield or Field Audit Trail licenses. The AdditionalFieldHistory feature cap was presumably set when the platform limit was 60 (20 base + 40 additional) and has not been updated to reflect the Spring '26 increase to 200.
Related: #1922 (similar issue where standard object pre-tracked fields were not accounted for in the feature budget).
System Information
json{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.132.14",
"nodeVersion": "node-v22.17.1",
"osVersion": "Windows_NT 10.0.26100",
"rootPath": "C:\Users\dalden\AppData\Roaming\npm\node_modules\@salesforce\cli",
"shell": "powershell",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.45 (core)",
"@oclif/plugin-commands 4.1.47 (core)",
"@oclif/plugin-help 6.2.44 (core)",
"@oclif/plugin-not-found 3.2.80 (core)",
"@oclif/plugin-plugins 5.4.61 (core)",
"@oclif/plugin-search 1.2.44 (core)",
"@oclif/plugin-update 4.7.32 (core)",
"@oclif/plugin-version 2.2.42 (core)",
"@oclif/plugin-warn-if-update-available 3.1.60 (core)",
"@oclif/plugin-which 3.2.49 (core)",
"@salesforce/cli 2.132.14 (core)",
"agent 1.32.22 (core)",
"apex 3.9.21 (core)",
"api 1.3.20 (core)",
"auth 4.3.7 (core)",
"data 4.0.92 (core)",
"deploy-retrieve 3.24.33 (core)",
"info 3.4.123 (core)",
"limits 3.3.84 (core)",
"marketplace 1.3.18 (core)",
"org 5.10.0 (core)",
"packaging 2.27.5 (core)",
"schema 3.3.105 (core)",
"settings 2.4.69 (core)",
"sobject 1.4.98 (core)",
"source 3.5.21 (user) published 597 days ago (Sat Sep 14 2024)",
"telemetry 3.8.13 (core)",
"templates 56.16.0 (core)",
"trust 3.7.124 (core)",
"user 3.8.3 (core)"
]
}
Apologies if I've missed something obvious here — happy to be pointed in the right direction if there's already a way to get a scratch org up to the 200-field limit.
The AdditionalFieldHistory scratch org feature is capped at a maximum value of 40 (yielding 60 total tracked fields when combined with the base 20). This limit does not reflect the current platform capability: as of Spring '26 (API v66.0), Field Audit Trail supports up to 200 tracked fields per object. The feature cap should be raised to 180 to match (20 base + 180 additional = 200).
Steps To Reproduce
Create a scratch org definition file with AdditionalFieldHistory set to a value greater than 40, e.g.:
json{
"edition": "Enterprise",
"features": ["AdditionalFieldHistory:100"]
}
Run sf org create scratch -f
Expected result
Scratch org is created with support for up to 200 tracked fields per object, consistent with the Field Audit Trail limit introduced in Spring '26.
Actual result
INVALID_INPUT: 100 is not a valid quantity for the Features value AdditionalFieldHistory.
Scratch org creation fails. The maximum accepted value is 40.
Additional information
The Field Audit Trail documentation (help.salesforce.com) now states a limit of 200 tracked fields per object for orgs with Salesforce Shield or Field Audit Trail licenses. The AdditionalFieldHistory feature cap was presumably set when the platform limit was 60 (20 base + 40 additional) and has not been updated to reflect the Spring '26 increase to 200.
Related: #1922 (similar issue where standard object pre-tracked fields were not accounted for in the feature budget).
System Information
json{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.132.14",
"nodeVersion": "node-v22.17.1",
"osVersion": "Windows_NT 10.0.26100",
"rootPath": "C:\Users\dalden\AppData\Roaming\npm\node_modules\@salesforce\cli",
"shell": "powershell",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.45 (core)",
"@oclif/plugin-commands 4.1.47 (core)",
"@oclif/plugin-help 6.2.44 (core)",
"@oclif/plugin-not-found 3.2.80 (core)",
"@oclif/plugin-plugins 5.4.61 (core)",
"@oclif/plugin-search 1.2.44 (core)",
"@oclif/plugin-update 4.7.32 (core)",
"@oclif/plugin-version 2.2.42 (core)",
"@oclif/plugin-warn-if-update-available 3.1.60 (core)",
"@oclif/plugin-which 3.2.49 (core)",
"@salesforce/cli 2.132.14 (core)",
"agent 1.32.22 (core)",
"apex 3.9.21 (core)",
"api 1.3.20 (core)",
"auth 4.3.7 (core)",
"data 4.0.92 (core)",
"deploy-retrieve 3.24.33 (core)",
"info 3.4.123 (core)",
"limits 3.3.84 (core)",
"marketplace 1.3.18 (core)",
"org 5.10.0 (core)",
"packaging 2.27.5 (core)",
"schema 3.3.105 (core)",
"settings 2.4.69 (core)",
"sobject 1.4.98 (core)",
"source 3.5.21 (user) published 597 days ago (Sat Sep 14 2024)",
"telemetry 3.8.13 (core)",
"templates 56.16.0 (core)",
"trust 3.7.124 (core)",
"user 3.8.3 (core)"
]
}
Apologies if I've missed something obvious here — happy to be pointed in the right direction if there's already a way to get a scratch org up to the 200-field limit.