Unable to deploy Flex Prompt Template with Flow Reference : Error [Prompt_Template_Name] Failure to create template: [Prompt_Template_Name], Caused by: null devname

[prakash-purswani]

Note
Before you submit your issue, make sure that:

• You're using the latest version of Salesforce CLI.
• You've searched both open and closed issues for related posts.
• You've used the doctor command to diagnose common issues.
• You understand that GitHub Issues don't adhere to any agreement or SLA.
  • If you require immediate assistance, use official channels such as Salesforce Customer Support.

Summary

I am trying to deploy a flex prompt template with flow references but it fails with error Error [Prompt_Template_Name] Failure to create template: [Prompt_Template_Name], Caused by: null devname.

It works if we remove the flow reference. Also, Sales Email type of prompt template gets deployed without any issue with a flow reference.

Steps To Reproduce

IMPORTANT
Provide a repository that's configured to reproduce the issue. If you are unable to provide a repo, please explain why not. The more info we have from the start, the faster we can resolve your issue.
We may close your issue if you don't include proper instructions.

• Generate a project with sf project generate or fork dreamhouse-lwc.
• Provide detailed step-by-step instructions on how to reproduce the issue.

Tip

use sf doctor --create-issue to automatically fill the required information

1. Create a flex prompt template
2. Create a prompt template triggered flow.
3. Refer the prompt template triggered flow in the flex prompt template.
4. Retrieve the same in VS Code and try to deploy in another environment.

Expected result

Both Flow and Flex Template should be deployed successfully.

Actual result

Fails to deploy the prompt template.

Additional information

System Information

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.56.7",
  "nodeVersion": "node-v20.16.0",
  "osVersion": "Windows_NT 10.0.22621",
  "rootPath": "C:\\Users\\prakash.purswani\\AppData\\Local\\sf\\client\\2.56.7-94d8766",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.0 (core)",
    "@oclif/plugin-commands 4.0.11 (core)",
    "@oclif/plugin-help 6.2.8 (core)",
    "@oclif/plugin-not-found 3.2.16 (core)",
    "@oclif/plugin-plugins 5.4.4 (core)",
    "@oclif/plugin-search 1.2.5 (core)",
    "@oclif/plugin-update 4.5.3 (core)",
    "@oclif/plugin-version 2.2.10 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.11 (core)",
    "@oclif/plugin-which 3.2.10 (core)",
    "@salesforce/cli 2.56.7 (core)",
    "apex 3.4.2 (core)",
    "api 1.1.0 (core)",
    "auth 3.6.48 (core)",
    "data 3.6.1 (core)",
    "deploy-retrieve 3.10.1 (core)",
    "info 3.3.29 (core)",
    "limits 3.3.25 (core)",
    "marketplace 1.2.22 (core)",
    "org 4.5.4 (core)",
    "packaging 2.8.0 (core)",
    "schema 3.3.24 (core)",
    "settings 2.3.13 (core)",
    "signups 2.5.9 (user) published 10 days ago (Sun Aug 18 2024) (latest is 2.5.10)",        
    "sobject 1.4.29 (core)",
    "source 3.5.14 (core)",
    "telemetry 3.6.7 (core)",
    "templates 56.3.12 (core)",
    "trust 3.7.23 (core)",
    "user 3.5.25 (core)"
  ]
}

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[github-actions]

Hello @prakash-purswani 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!

[cristiand391]

@prakash-purswani I couldn't get an org to repro this but that look like a server error coming from the Metadata API.

I would suggest opening a case to get more attention, I looked internally for more similar reports but couldn't find any known issue/reported bug yet.

[ls-Quentin-Monceau]

Hi @prakash-purswani,
Did you find any additional information regarding this error, or were you able to fix it?
Thanks!