Skip to content

Dependencies deployment bug ? v2.140.4 #3581

Description

@AmineIdTa

Summary

Since the lastest release update the 13th and 14th june, when using the command
sf project deploy -d force-app/main, something wierd happens with genAiPromptTemplates

For more context, we deployed a screen flow that uses a genAiPrompt (it was like 5 weeks ago, smth like that). But since the release, the same command return this issue
Image

Two possibiilties:

  • Either the .promptRepsone does not exist anymore (which is not, I checked and still present as an ouptput var)
  • The prompt is not deployed, I mean not deployed before the flow -> which is wierd, cuz' when we deploy some metadata whith dependencies, the dependencies are deployed first then the main cmps.

Well, when I deployed the genAiPrompt before the full package, it worked

I dont know if the cli is responsilbe or it's some salesforce's dark magic surprise (like what we see after each release) ?

System Information

{
"architecture": "wsl-x64",
"cliVersion": "@salesforce/cli/2.140.4",
"nodeVersion": "node-v24.11.1",
"osVersion": "Linux 5.15.167.4-microsoft-standard-WSL2",
"rootPath": "/home/aidrissi/.nvm/versions/node/v24.11.1/lib/node_modules/@salesforce/cli",
"shell": "bash",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.50 (core)",
"@oclif/plugin-commands 4.1.57 (core)",
"@oclif/plugin-help 6.2.50 (core)",
"@oclif/plugin-not-found 3.2.87 (core)",
"@oclif/plugin-plugins 5.4.74 (core)",
"@oclif/plugin-search 1.2.50 (core)",
"@oclif/plugin-update 4.7.48 (core)",
"@oclif/plugin-version 2.2.47 (core)",
"@oclif/plugin-warn-if-update-available 3.1.65 (core)",
"@oclif/plugin-which 3.2.55 (core)",
"@salesforce/cli 2.140.4 (core)",
"agent 1.42.1 (core)",
"apex 3.9.34 (core)",
"api 1.3.40 (core)",
"auth 4.4.2 (core)",
"code-analyzer 5.0.0 (user) published 413 days ago (Tue Apr 29 2025) (latest is 5.13.0)",
"data 4.0.106 (core)",
"deploy-retrieve 3.24.54 (core)",
"info 3.4.140 (core)",
"limits 3.3.93 (core)",
"marketplace 1.3.31 (core)",
"org 5.11.8 (core)",
"packaging 2.29.3 (core)",
"schema 3.3.117 (core)",
"settings 2.4.84 (core)",
"signups 2.6.54 (user) published 228 days ago (Sat Nov 01 2025) (latest is 2.6.72)",
"sobject 1.4.112 (core)",
"telemetry 3.8.26 (core)",
"templates 56.18.4 (core)",
"trust 3.8.19 (core)",
"user 3.10.1 (core)",
"@salesforce/sfdx-scanner 4.12.0 (user) published 413 days ago (Tue Apr 29 2025)",
"sfdx-git-delta 6.18.0 (user) published 302 days ago (Tue Aug 19 2025) (latest is 6.31.0)"
]
}

{
  "architecture": "wsl-x64",
  "cliVersion": "@salesforce/cli/2.140.4",
  "nodeVersion": "node-v24.11.1"
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    investigatingWe're actively investigating this issueowned by another teamThe Salesforce CLI team does not own this work but will pass on the information to the correct team.validatedVersion information for this issue has been validated

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions