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

Timeout or long time for retrieve and diff functions #5654

Closed
SarveshSprk opened this issue Jun 21, 2024 · 15 comments
Closed

Timeout or long time for retrieve and diff functions #5654

SarveshSprk opened this issue Jun 21, 2024 · 15 comments
Labels
status:owned by another team We are maintaining this feedback for visibility but it is not within control of our team type:bug validated

Comments

@SarveshSprk
Copy link

SarveshSprk commented Jun 21, 2024

Summary

VSCode retrieve or diff time varies a lot and mostly on the longer side even leading to timeout in Sandbox.

Steps To Reproduce:

  1. Open VSCode
  2. After extensions are loaded, try to retrieve single file/component using right click and select retrieve.

Expected result

Retrieve or Diff function to execute within few seconds.

Actual result

Most of the time it time outs, and sometimes it takes 6-7 mins.

Salesforce Extension Version in VS Code: 61.1.2

Salesforce CLI Version: 2.45.6

OS and version: Windows 11 Enterprise 64 bit 10.0.22621

VS Code version: 1.90.2

Most recent version of the extensions where this was working: Not sure, the issue is happening from two weeks.

@svc-idee-bot
Copy link
Collaborator

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.

@RCMoonpie
Copy link

RCMoonpie commented Jun 21, 2024

I, too, suddenly had a seemingly related issue today when attempting to retrieve a Custom Metadata Type that was newly created via UI in a sandbox and which did not yet exist in my local project.

Issue Details

Initial

Command

sf project retrieve start --metadata CustomObject:New_CMDT__mdt

Output while running

>> Warning: @salesforce/cli update available from 2.34.7 to 2.46.6
Retrieving v59.0 metadata from [email protected] using the v61.0 SOAP API
Preparing retrieve request... | Pending

NOTE: Spinner between "request..." and "Pending" was spinning the entire time

Result

After an estimated 60-90 seconds, pressed Ctrl + C in terminal to abort

Output after abort:

Preparing retrieve request... done
C:\Programs Portable\node-v20.10.0-win-x64\node_modules\@salesforce\cli\node_modules\@olif\core\lib\errors\index.js:20
    throw new exit_1.ExitError(code);
    ^
    
ExitError: EEXIT: 130
    at RetrieveMetadata.exit (C:\Programs Portable\node-v20.10.0-winx64\node-modules\@salesfore\cli\node_modules\@oclif\core\lib\command.js:180:16)
    at process.<anonyous> (file:///C:/Programs%20Portable/node-v20.10.0-winx64/node_modules/@salesforce/cli/node_modules/@salesforce/sf-plugins-core/lib/sfCommand.js:262:22)
    at process.emit (node:events:526:35) {
  code: 'EEXIT',
  oclif: { exit: 130 },
  skipOclifErrorHandling: undefined,
  suggestions: undefined
}

Node.js v20.10.0

Notes

  • Right-click diff on metadata existing in local project worked fine
  • Right-click deployment of metadata from local project worked fine

System info

Salesforce Extension Version in VS Code: 61.1.2 (updated yesterday, 20 June 2024)
Salesforce CLI Version: @salesforce/cli/2.34.7 win32-x64 node-v20.10.0
OS and version: Windoze x64 10.0.19045
VS Code version: 1.88.1
Most recent version of the extensions where this was working: Unknown -- I do not know what version I was on before updating yesterday

Next Step

  • Retried same command : same result

Next Step

  • Restarted VS Code
  • Retried same command : SUCCESS

@daphne-sfdc
Copy link
Contributor

Hi @SarveshZap, Can we get some info about your org shape? For example, number of Apex classes, number of LWC components, number of custom objects, etc. Can we also get the org id of your sandbox and the org id of the production org that created the sandbox?

@diyer
Copy link
Collaborator

diyer commented Jun 21, 2024

@RCMoonpie looks like you are running retrieve with cli command and not with VS Code extension. If the issue is with cli, please report it on https://github.com/forcedotcom/cli

Copy link

This issue has not received a response in 3 days. It will auto-close in 2 days unless a response is posted.

@github-actions github-actions bot added the stale label Jun 28, 2024
@SarveshSprk
Copy link
Author

SarveshSprk commented Jun 28, 2024

Hi @SarveshZap, Can we get some info about your org shape? For example, number of Apex classes, number of LWC components, number of custom objects, etc. Can we also get the org id of your sandbox and the org id of the production org that created the sandbox?

Hello @daphne-sfdc, I am not sure if I can give you org id of sandboxes. Though the org has many components including number of custom objects, apex classes and LWC. The applications is customized on higher side. It used to take few seconds without single occurrence of delay before last two weeks.

We tried to reach out salesforce support and got this article in response which has no ETA or workaround :(
https://issues.salesforce.com/issue/a028c00000yGOhWAAW/intermittent-long-wait-time-for-metadata-retrieval-using-mdapisfdc-cli-post-migrating-to-hyperforce

@daphne-sfdc
Copy link
Contributor

Hello @SarveshZap, In order to investigate the logs for your issue on our systems, we need the org id of your sandbox. If you would prefer not to send us the org id on a public forum, please email it to us at [email protected].

@daphne-sfdc daphne-sfdc removed the stale label Jun 28, 2024
@SarveshSprk
Copy link
Author

SarveshSprk commented Jul 1, 2024

Hello @SarveshZap, In order to investigate the logs for your issue on our systems, we need the org id of your sandbox. If you would prefer not to send us the org id on a public forum, please email it to us at [email protected].

@daphne-sfdc Thanks for sharing email id, but it seems this email id is invalid: [email protected]
Could you please check again and confirm?

@daphne-sfdc
Copy link
Contributor

@SarveshSprk Sorry for the typo - it's [email protected].

@SarveshSprk
Copy link
Author

@SarveshSprk Sorry for the typo - it's [email protected].

@daphne-sfdc Sent an email to that address few mins ago. Kindly check.

@daphne-sfdc
Copy link
Contributor

@SarveshSprk Yes I received the email. Thank you.

@SarveshSprk
Copy link
Author

@daphne-sfdc Just wanted to check-in if there is any diagnosis / update on this issue with continuing conversation. Thanks.

Copy link

git2gus bot commented Jul 9, 2024

This issue has been linked to a new work item: W-16198550

@daphne-sfdc daphne-sfdc added the status:owned by another team We are maintaining this feedback for visibility but it is not within control of our team label Jul 9, 2024
@daphne-sfdc
Copy link
Contributor

Closing this issue as the delay is on the server side.

@svc-idee-bot
Copy link
Collaborator

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:owned by another team We are maintaining this feedback for visibility but it is not within control of our team type:bug validated
Projects
None yet
Development

No branches or pull requests

5 participants