Skip to content

Receiving "Error (SfError): undefinedComponentSet" for --dry-run validation runs #3336

@milesdinneen

Description

@milesdinneen

Summary

Since v2.94.6 validation runs against [UE org] sandboxes refreshed since late June (at least since 26th June but maybe before) using --dry-run param are failing with response Error (SfError): undefinedComponentSet. Discovered first on pipelines automatically using latest version and now locally on a laptop after update to test this.

Steps To Reproduce

  1. Run sf project deploy start --ignore-conflicts --wait 60 --target-org envName --dry-run or even simply sf project deploy start --dry-run --target-org envName
  2. Immediately receive error Error (SfError): undefinedComponentSet

Expected result

The SF CLI should perform a validation run only against the target org

Actual result

Received only error of Error (SfError): undefinedComponentSet

Additional information

Works in 2.94.5 but fails in 2.94.6 onwards, and is still failing with latest release candidate. Removing --dry-run from the command in 2.94.6+ stops the error, and code is deployed to the target org. Issue seems solely related to --dry-run parameter.

For any sandboxes refreshed before end June the command works as expected. Recently refreshed sandboxes that don't work and older ones that do are all on the same Salesforce instance. To confirm, with SF CLI v2.94.5 or below there is no issue for any sandbox, but since 2.94.6 (and related PR 1372) there is for the newly refreshed boxes.

Error in user .sf log file:
{"level":50,"time":1751644737806,"name":"sf:oclif","msg":"SfError: undefinedComponentSet\n at SfCommandError.from (file:///C:/Users/username/AppData/Local/sf/client/2.95.6-b4d51b1/node_modules/@salesforce/sf-plugins-core/lib/SfCommandError.js:39:16)\n at DeployMetadata.catch (file:///C:/Users/username/AppData/Local/sf/client/2.95.6-b4d51b1/node_modules/@salesforce/sf-plugins-core/lib/sfCommand.js:323:47)\n at DeployMetadata.catch (file:///C:/Users/username/AppData/Local/sf/client/2.95.6-b4d51b1/node_modules/@salesforce/plugin-deploy-retrieve/lib/commands/project/deploy/start.js:272:27)\n at DeployMetadata._run (C:/Users/username/AppData/Local/sf/client/2.95.6-b4d51b1/node_modules/@oclif/core/lib/command.js:185:29)\n at async Config.runCommand (C:/Users/username/AppData/Local/sf/client/2.95.6-b4d51b1/node_modules/@oclif/core/lib/config/config.js:456:25)\n at async run (C:/Users/username/AppData/Local/sf/client/2.95.6-b4d51b1/node_modules/@oclif/core/lib/main.js:96:16)\n at async file:///C:/Users/username/AppData/Local/sf/client/2.95.6-b4d51b1/bin/run.js:15:1"}

Laptop info below but also failing on CI/CD on Azure using vmImage: ubuntu-latest

System Information

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.95.6",
  "nodeVersion": "node-v22.16.0",
  "osVersion": "Windows_NT 10.0.22631",
  "rootPath": "C:\\Users\\username\\AppData\\Local\\sf\\client\\2.95.6-b4d51b1",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.31 (core)",
    "@oclif/plugin-commands 4.1.26 (core)",
    "@oclif/plugin-help 6.2.29 (core)",
    "@oclif/plugin-not-found 3.2.57 (core)",
    "@oclif/plugin-plugins 5.4.42 (core)",
    "@oclif/plugin-search 1.2.25 (core)",
    "@oclif/plugin-update 4.6.45 (core)",
    "@oclif/plugin-version 2.2.30 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.42 (core)",
    "@oclif/plugin-which 3.2.37 (core)",
    "@salesforce/cli 2.95.6 (core)",
    "agent 1.23.1 (core)",
    "apex 3.6.19 (core)",
    "api 1.3.3 (core)",
    "auth 3.7.3 (core)",
    "code-analyzer 5.0.0 (user)",
    "data 4.0.40 (core)",
    "deploy-retrieve 3.22.27 (core)",
    "info 3.4.69 (core)",
    "limits 3.3.57 (core)",
    "marketplace 1.3.8 (core)",
    "org 5.9.0 (core)",
    "packaging 2.13.2 (user)",
    "schema 3.3.68 (core)",
    "settings 2.4.32 (core)",
    "sobject 1.4.63 (core)",
    "telemetry 3.6.45 (core)",
    "templates 56.3.52 (core)",
    "trust 3.7.101 (core)",
    "user 3.6.26 (core)",
    "@salesforce/sfdx-scanner 4.12.0 (user)"
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    Awaiting ReleaseA fix has been validated and merged, check `nightly` or `latest-rc` buildsbugIssue or pull request that identifies or fixes a bugvalidatedVersion information for this issue has been validated

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions