Unable to report on quick-deployed deployment due to NoMatchingJobIdError

[YodaDaCoda]

Summary

In our CI we quick-deploy a previously validated deployment id if available. sf project deploy quick works fine, but subsequently attempting to report on the deployment throws NoMatchingJobIdError

Steps To Reproduce

1. obtain a validated deployment id for quick-deploy
2. on a different machine, or in a separate environment, run the below command to init the quick-deploy and get the id of the resulting deployment
   sf project deploy quick --json --async --job-id "${quick_deploy_id}" >"${quick_deploy_file}"
3. parse $quick_deploy_file to get the resulting deployment id
4. attempt to output status of the quick-deployment using the new deployment id
   sf project deploy resume --job-id "${deploy_id}"
5. note the error
   Error (NoMatchingJobIdError): No matching job found in cache for ID: <deploy_id>

Expected result

Even if the deploy_id isn't present in the cache, I expect the cli to make the api request to the target-org for the status of the deployment.

Actual result

The error is thrown.

Additional information

System Information

Bash inside an Ubuntu 24.04 container on Azure Devops Pipelines

{
  "architecture": "linux-x64",
  "cliVersion": "@salesforce/cli/2.71.6",
  "nodeVersion": "node-v22.13.0",
  "osVersion": "Linux 6.11.11-1-MANJARO",
  "rootPath": "/home/will/github/x/node_modules/@salesforce/cli",
  "shell": "bash",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.14 (core)",
    "@oclif/plugin-commands 4.1.14 (core)",
    "@oclif/plugin-help 6.2.19 (core)",
    "@oclif/plugin-not-found 3.2.31 (core)",
    "@oclif/plugin-plugins 5.4.22 (core)",
    "@oclif/plugin-search 1.2.17 (core)",
    "@oclif/plugin-update 4.6.18 (core)",
    "@oclif/plugin-version 2.2.18 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.28 (core)",
    "@oclif/plugin-which 3.2.21 (core)",
    "@pdfbutler/migration-cli 0.0.19 (link) /home/will/github/x/node_modules/@pdfbutler/migration-cli",
    "@salesforce/cli 2.71.6 (core)",
    "apex 3.6.8 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.82 (core)",
    "community 3.3.8 (link) /home/will/github/x/node_modules/@salesforce/plugin-community",
    "data 3.13.5 (core)",
    "deploy-retrieve 3.16.0 (core)",
    "info 3.4.29 (core)",
    "limits 3.3.43 (core)",
    "marketplace 1.3.7 (core)",
    "org 5.2.11 (core)",
    "packaging 2.9.7 (core)",
    "schema 3.3.45 (core)",
    "settings 2.4.9 (core)",
    "sobject 1.4.46 (core)",
    "telemetry 3.6.27 (core)",
    "templates 56.3.34 (core)",
    "trust 3.7.51 (core)",
    "user 3.6.5 (core)",
    "sfdmu 4.37.0 (user) published 54 days ago (Thu Nov 28 2024) (latest is 4.38.0)",
    "sfdx-git-delta 6.0.2 (link) /home/will/github/x/node_modules/sfdx-git-delta",
    "sfdx-hardis 5.15.2 (link) /home/will/github/x/node_modules/sfdx-hardis"
  ]
}

[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 @YodaDaCoda 👋 None of the versions of sf you shared match the latest release.

Shared: 2.71.6
Latest: 2.72.21

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[YodaDaCoda]

issue still exists on the latest stable

{
  "architecture": "linux-x64",
  "cliVersion": "@salesforce/cli/2.72.21",
  "nodeVersion": "node-v22.13.0",
  "osVersion": "Linux 6.11.11-1-MANJARO",
  "rootPath": "/home/will/github/x/node_modules/@salesforce/cli",
  "shell": "bash",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.16 (core)",
    "@oclif/plugin-commands 4.1.15 (core)",
    "@oclif/plugin-help 6.2.20 (core)",
    "@oclif/plugin-not-found 3.2.33 (core)",
    "@oclif/plugin-plugins 5.4.24 (core)",
    "@oclif/plugin-search 1.2.17 (core)",
    "@oclif/plugin-update 4.6.21 (core)",
    "@oclif/plugin-version 2.2.19 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.29 (core)",
    "@oclif/plugin-which 3.2.23 (core)",
    "@pdfbutler/migration-cli 0.0.19 (link) /home/will/github/x/node_modules/@pdfbutler/migration-cli",
    "@salesforce/cli 2.72.21 (core)",
    "apex 3.6.8 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.85 (core)",
    "community 3.3.8 (link) /home/will/github/x/node_modules/@salesforce/plugin-community",
    "data 4.0.1 (core)",
    "deploy-retrieve 3.17.0 (core)",
    "info 3.4.30 (core)",
    "limits 3.3.43 (core)",
    "marketplace 1.3.7 (core)",
    "org 5.2.16 (core)",
    "packaging 2.9.10 (core)",
    "schema 3.3.45 (core)",
    "settings 2.4.9 (core)",
    "sobject 1.4.48 (core)",
    "telemetry 3.6.29 (core)",
    "templates 56.3.34 (core)",
    "trust 3.7.53 (core)",
    "user 3.6.5 (core)",
    "sfdmu 4.37.0 (user) published 54 days ago (Thu Nov 28 2024) (latest is 4.38.0)",
    "sfdx-git-delta 6.0.2 (link) /home/will/github/x/node_modules/sfdx-git-delta",
    "sfdx-hardis 5.15.2 (link) /home/will/github/x/node_modules/sfdx-hardis"
  ]
}

[cristiand391]

This is by design, project deploy resume can only resume local deployments (it doesn't even take --target-org so it can't resolve a deploy ID that's didn't start in the same machine).
Aside from returning the deployment status, it will update your local source tracking info (if enabled).

You should use project deploy report instead to check the status.

[YodaDaCoda]

Thanks @cristiand391 you're absolutely correct, I've been using the wrong command for my use-case.