I am trying to fetch the extensions from a 2019.2 ...
# suitecommerce
k
I am trying to fetch the extensions from a 2019.2 SCA website, and I continue to get errors like “SSS_REQUEST_LIMIT_EXCEEDED” and Error in plugin “gulp extension:fetch” Message:  Could not download all the extension files. I have tried using the extension developers tools zip file from 2018.2.1, 2019.2 and 2020.1. They all encounter the same problem. Any ideas on what the cause/fix might be?
m
I just had a similar issue with this. We had to delete our theme and re upload it. That seemed to fix it.
k
How did you delete the theme?
My issue is the extensions. Were you having issues with the extension fetch or theme fetch?
t
I'm running into the same issue and NS support is giving me the run around
w
this has been a recurring issue recently, with no confirmed resolution. This seems to start frequently when NS enforced the concurrency limit for the account, since the deploy uses RESTlet I guess it’s fighting over inbound request thread, but I have seen clients without heavy integration that encounters this issue as well (so not really sure). My solution for this is just keep retrying the deploy.😞
h
Hey @Keith Fetterman - I had this issue previously on a customer's account. It was because there was an integration on the account that seemed to hog the bandwidth required to pull the extensions. If you go to Setup > Integrations > Integration Governance, you should see a list of integrations (that being said I was unable to access this page this morning, and instead went to Setup > Integrations > Manage Integrations and checked each of the integrations listed there to find the one I was looking for). The account I was working in at the time has a limit of 5 concurrent integrations streams and one of the integrations was setup to use 4 of those streams. I edited that integration and reduced the Concurrency Limit and Max Concurrency Limit fields from 4 down to 1 or 2. Then I ran my extension fetch command and after it had completed I updated the integration back to it's original amount of 4. Hope that helps!
👍 2
k
@wbermudo and @Harley, thank both for the information. This is very helpful. Since the error was related to concurrency, I looked at the APM concurrency monitor and noticed that they had a high “Total Exceeded Concurrency” number, which was around 599 for the past 3 days. @Harley, thanks for telling me how to locate and modify their concurrency temporarily so I can do my deployments.
👍 2
@Harley, your instructions worked. I found an integration that had concurrency limit set to 4. I reduced it to 2 and I could deploy after that. The account limit was 5.
h
Glad to hear it was able to resolve your issue 🙂