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

CLIError: timed out #1736

Closed
faheemaligit opened this issue Oct 4, 2022 · 4 comments
Closed

CLIError: timed out #1736

faheemaligit opened this issue Oct 4, 2022 · 4 comments
Labels
more information required Issue requires more information or a response from the customer stale

Comments

@faheemaligit
Copy link

I don't know why I frequently face these errors while taking metadata backup

CLIError: timed out

And after that, it stuck in List metadata and did not continue for backup, on some days it work fine on others it throws an error.
Sometimes things got stopped in Describe metadata step too.
I hope this is a common issue that needs a fix.

If anyone has a fix for these errors, please comment with your working solutions #1511 :)
image

@shetzel shetzel added the more information required Issue requires more information or a response from the customer label Oct 4, 2022
@shetzel
Copy link
Contributor

shetzel commented Oct 4, 2022

Thank you for posting. We're going to need more information. At a minimum, we will need your CLI and plugin versions. You can get that from running this command: sfdx version --verbose and posting it here. We'll also need the exact command (including all parameters) that causes the problem and the error. It will help us even more to provide a stack trace if possible. Alternatively, you can get all of this information by running, sfdx doctor --command "[insert command here]" which will generate several files and have some suggestions on what might be wrong. From your post I can see that you're on CLI version 7.163.0 and the latest is 7.170.0, so you'll want to update.

@github-actions
Copy link

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

@github-actions github-actions bot added the stale label Oct 12, 2022
@nvuillam
Copy link

@shetzel same happening here, metadata backup jobs failing because of timeouts, on some projects but not all

@github-actions github-actions bot removed the stale label Oct 18, 2022
@github-actions
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more information required Issue requires more information or a response from the customer stale
Projects
None yet
Development

No branches or pull requests

3 participants