Skip to content

[BUG]: sf project delete source -m "Flow:XYZ` returns insufficient access rights on cross-reference id #3684

Open

Description

@pkozuchowski

Before You Submit

  • I'm using the latest version of Salesforce CLI
  • I've searched the existing issues
  • I've run sf doctor to diagnose common issues

Related Issue

No response

Command

sf project delete source

Org Type

Sandbox

Did this work before?

No, this is a new bug

Last Working Version

No response

Summary

When I'm trying to delete Flow entirely, it always return insufficient access rights on cross-reference id even though I'm an admin and I have all rights to the flow.
I can delete the same flow without any issues from the UI.

sf project delete source -r -m "Flow:FO_Sampling_Flow"

Component Failures [1]
┌───────┬──────────────────┬──────────────────────────────────────────────────┐
│ Type  │ Name             │ Problem                                          │
├───────┼──────────────────┼──────────────────────────────────────────────────┤
│ Error │ FO_Sampling_Flow │ insufficient access rights on cross-reference id │
└───────┴──────────────────┴──────────────────────────────────────────────────┘

Repository to Reproduce

No response

Steps to reproduce

  1. Create screen flow "TestDeleteIssues". It doesn't need to be activated, just saved.
  2. sf project delete source -r -m "Flow:TestDeleteIssues"
  3. Notice error

Expected Result

Flow and all flow versions should be deleted., regardless of activation status.

Actual Result

Component Failures [1]
┌───────┬──────────────────┬──────────────────────────────────────────────────┐
│ Type  │ Name             │ Problem                                          │
├───────┼──────────────────┼──────────────────────────────────────────────────┤
│ Error │ TestDeleteIssues │ insufficient access rights on cross-reference id │
└───────┴──────────────────┴──────────────────────────────────────────────────┘

Error Message

insufficient access rights on cross-reference id

System Information

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.157.8",
  "nodeVersion": "node-v24.20.0",
  "osVersion": "Windows_NT 10.0.26300",
  "rootPath": "C:\\Users\\piotr\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\cli",
  "shell": "cmd.exe",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 4.0.6 (core)",
    "@oclif/plugin-commands 5.0.6 (core)",
    "@oclif/plugin-help 7.0.6 (core)",
    "@oclif/plugin-not-found 4.0.7 (core)",
    "@oclif/plugin-plugins 7.0.13 (core)",
    "@oclif/plugin-search 2.0.9 (core)",
    "@oclif/plugin-update 5.0.10 (core)",
    "@oclif/plugin-version 3.0.7 (core)",
    "@oclif/plugin-warn-if-update-available 4.0.5 (core)",
    "@oclif/plugin-which 4.0.6 (core)",
    "@salesforce/cli 2.157.8 (core)",
    "agent 2.2.3 (core)",
    "apex 4.4.4 (core)",
    "api 2.0.24 (core)",
    "auth 6.0.0 (core)",
    "code-analyzer 5.16.0 (user)",
    "data 5.1.24 (core)",
    "deploy-retrieve 4.3.2 (core)",
    "info 4.0.22 (core)",
    "lightning-dev 6.2.19 (user)",
    "limits 4.0.6 (core)",
    "marketplace 2.0.23 (core)",
    "org 7.0.10 (core)",
    "packaging 3.0.17 (core)",
    "schema 4.0.16 (core)",
    "settings 3.0.22 (core)",
    "sobject 2.0.20 (core)",
    "telemetry 4.2.4 (core)",
    "templates 57.5.0 (core)",
    "trust 4.0.28 (core)",
    "user 6.0.6 (core)",
    "sfdmu 5.8.0 (user)",
    "sfdx-git-delta 6.45.1 (user)"
  ]
}

Additional Information

No response

Screenshots or Log Files

No response

Activity

  1. github-actions commented on Nov 6, 2026

    @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.

  2. added
    validatedVersion information for this issue has been validated
    on Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:mdapiThis is an issue for MDAPI server side team.investigatingWe're actively investigating this issuevalidatedVersion 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