Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployments and Retrieves are not working #2632

Closed
rrosset91 opened this issue Jan 4, 2024 · 5 comments
Closed

Deployments and Retrieves are not working #2632

rrosset91 opened this issue Jan 4, 2024 · 5 comments
Labels
investigating We're actively investigating this issue validated Version information for this issue has been validated

Comments

@rrosset91
Copy link

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

Both from sfdx cli or cli integration extension from VSCODE, the DEPLOY and RETRIEVE actions are resulting in a long time running operation with no error displayed, it just keeps loading, without further action.
Its important to mention that apparently this is happening on all sandboxes of my organization and also using other sources such as Workbench. This morning I tried to do a retrieve from workbench (Since vscode was with this issue) and it took 20 minutes loading and then I just gave up.

Steps To Reproduce

On VSCODE:
Right click on any metadata, go to Deploy Source to Org (Or Retrieve Source from Org)
On WORKBENCH:
Select any package.xml that contains metadata info, and try to deploy it or retrieve it

Expected result

Source deployed (Or retrieved) successfully

Actual result

Loading for long time without further actions

System Information

Windows

PASTE_VERSION_OUTPUT_HERE

Additional information

image

@rrosset91 rrosset91 added the investigating We're actively investigating this issue label Jan 4, 2024
Copy link

github-actions bot commented Jan 4, 2024

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 github-actions bot added more information required Issue requires more information or a response from the customer and removed investigating We're actively investigating this issue labels Jan 4, 2024
Copy link

github-actions bot commented Jan 4, 2024

Hello @rrosset91 👋 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!

@rrosset91
Copy link
Author

{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.22.7",
"nodeVersion": "node-v20.10.0",
"osVersion": "Windows_NT 10.0.22621",
"rootPath": "C:\Users\RogerRosset\AppData\Local\sf\client\2.22.7-453215f",
"shell": "cmd.exe",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.3 (core)",
"@oclif/plugin-commands 3.0.7 (core)",
"@oclif/plugin-help 6.0.8 (core)",
"@oclif/plugin-not-found 3.0.5 (core)",
"@oclif/plugin-plugins 4.1.10 (core)",
"@oclif/plugin-search 1.0.8 (core)",
"@oclif/plugin-update 4.1.5 (core)",
"@oclif/plugin-version 2.0.9 (core)",
"@oclif/plugin-warn-if-update-available 3.0.6 (core)",
"@oclif/plugin-which 3.0.12 (core)",
"@salesforce/cli 2.22.7 (core)",
"apex 3.0.9 (core)",
"auth 3.0.12 (core)",
"data 3.0.6 (core)",
"deploy-retrieve 2.2.6 (core)",
"info 3.0.8 (core)",
"limits 3.0.6 (core)",
"marketplace 1.0.11 (core)",
"org 3.1.2 (core)",
"packaging 1.27.10 (core)",
"schema 3.0.8 (core)",
"settings 2.0.9 (core)",
"sobject 1.0.6 (core)",
"source 3.0.3 (core)",
"telemetry 3.1.6 (core)",
"templates 56.0.4 (core)",
"trust 3.2.0 (core)",
"user 3.1.1 (core)"
]
}

@github-actions github-actions bot added investigating We're actively investigating this issue validated Version information for this issue has been validated and removed more information required Issue requires more information or a response from the customer labels Jan 4, 2024
@1ktribble
Copy link

1ktribble commented Jan 4, 2024

This is also occurring for our team and we all have MacOS devices. This command uses the old sfdx force:source:deploy command instead of the new sf project deploy start command. When I tried using sf project deploy start instead, I received a different error about Unexpected child metadata ... found for parent type [CustomObject] for custom metadata records.

Our timeout is set to 10 minutes, and at times, deploying a single class surpasses that timeout limit. Prior to v59.0 of the SOAP API, deployments were near-instantaneous.

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.21.8",
  "nodeVersion": "node-v18.16.0",
  "osVersion": "Darwin 22.6.0",
  "rootPath": "/usr/local/lib/node_modules/@salesforce/cli",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.0.2 (core)",
    "@oclif/plugin-commands 3.0.7 (core)",
    "@oclif/plugin-help 6.0.7 (core)",
    "@oclif/plugin-not-found 3.0.4 (core)",
    "@oclif/plugin-plugins 4.1.9 (core)",
    "@oclif/plugin-search 1.0.8 (core)",
    "@oclif/plugin-update 4.1.4 (core)",
    "@oclif/plugin-version 2.0.8 (core)",
    "@oclif/plugin-warn-if-update-available 3.0.5 (core)",
    "@oclif/plugin-which 3.0.11 (core)",
    "@salesforce/cli 2.21.8 (core)",
    "apex 3.0.8 (core)",
    "auth 3.0.10 (core)",
    "data 3.0.5 (core)",
    "deploy-retrieve 2.2.3 (core)",
    "info 3.0.7 (core)",
    "limits 3.0.5 (core)",
    "marketplace 1.0.10 (core)",
    "org 3.1.1 (core)",
    "packaging 1.26.4 (user)",
    "schema 3.0.8 (core)",
    "settings 2.0.9 (core)",
    "sobject 1.0.5 (core)",
    "source 3.0.3 (core)",
    "telemetry 3.1.4 (core)",
    "templates 56.0.4 (core)",
    "trust 3.1.2 (core)",
    "user 3.1.0 (core)",
    "sfdx-git-delta 5.31.1 (user)",
    "sfpowerkit 6.1.0 (user)",
    "texei-sfdx-plugin 2.1.3 (user)"
  ]
}

@cristiand391
Copy link
Member

I'm going to close this as a dup of #2631

@cristiand391 cristiand391 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating We're actively investigating this issue validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

3 participants