- changed status to open
Listing metadata for connection stuck
I work in an organization with a lot of metadata.
Today I've had to recover the whole thing bit by bit.
However, when I try to open the retrieve panel, I'm now stuck with the message "Listing metadata for connection".
It works correctly for the same org but with less metadata retrieved.
Edit 17h30
Thank you for your help.
OK, I've added the requested setting.
Here are the impacted files but I only have one .log, next to that, some telemetry files
Edit 17h41
But before reinstalling, is it not strange that it works for the same org with less metadata?
I have attached the log, too.
Comments (15)
-
repo owner -
reporter - edited description
- attached log17h30.zip
-
repo owner Thanks for the new log. I can see where you set the debug log settings, but I’m not seeing anything being logged from that class. That class gets engaged immediately after the progress indicator is updated to “Listing metadata for connection …”, so it’s weird that it’s not emitting copious log content.
I truly hate to ask you to do this, but I’ve seen a number of strange issues recently caused by repeated in-place updates of the JetBrains IDE that were resolved simply by reinstalling the IDE. Do you mind uninstalling and reinstalling IntelliJ IDEA – don’t remove caches or config files and it’ll be seamless – and then trying to reproduce this behavior with the same debug logging enabled? It’s pretty quick to reinstall, and that will rule out a few things if it’s still present.
-
reporter - edited description
- attached Log17h41Working.zip
-
repo owner I’m not sure that I understand what you mean by “the same org with less metadata”. The org has the same metadata contents on both situations, correct? So what exactly is it that has less metadata in one situation vs. another?
Also, if you don’t mind, can you add new responses as part of the thread here so that it’s a top-down discussion? That way I can always refer back to your most recent response without having to go back to the original issue description.
-
reporter Uninstall / Reinstall done
Custom debug setup
Log will follow in next message.
I’m not sure that I understand what you mean by “the same org with less metadata”. The org has the same metadata contents on both situations, correct? So what exactly is it that has less metadata in one situation vs. another?
I mean I have 2 projects using the same connection.
The one that bug is the one in which I'm retrieving all the org's metadata.
The one that works is a project where there are only the main metadatas (APEX Classes etc). -
reporter - attached idea.log
-
repo owner Thanks. When you say “all of the org’s metadata”, do you mean literally every single metadata type/object, or do you mean all of the metadata that has been customized/added relative to the org’s initial state?
If you mean the former – every single metadata type/object from the org – I would strongly recommend against that. There are numerous bugs with Salesforce’s retrieval and deployment APIs where they’ll list certain metadata as being available, but it was either fail to retrieve or will retrieve but fail to deploy back to the exact same org, often resulting in opaque internal server errors.
If you mean the latter and you’ve configured an explicit subscription for the subset of all org metadata that distinctly defines your customizations to the org, can you estimate how large that subscription might be in terms of distinct metadata objects?
-
reporter The 1st option was being implemented, but even though I can follow your advice, I can no longer access the retrieve component selection panel.
We're not talking about the retrieve itself, but about the component selection panel -
reporter I've been thinking about your message.
I'm going to create a new project, get the elements I need, and then merge them into the project buggy, which already contains almost all the metadata.
I'm not sure if you want to close this ticket, but I don't really need a fix, especially if we assume that the error is on Salesforce's side.Thank you a lot
-
reporter - marked as minor
- edited description
-
repo owner Okay. Let me know how that goes. Obviously if it’s still an issue, please let me know that and we’ll continue digging into it to see where the issue lies and what can/needs to be done about it.
-
reporter I retrieved what I was missing and merged the elements.
It solves my situation.Let's close this, thank you
-
reporter - changed status to resolved
-
repo owner Okay, glad to hear. It’s still strange that things would just hang. If you do see that behavior again, please let me know.
- Log in to comment
Hi. I apologize for the issue. Thanks for the log, but unfortunately it's not showing anything useful. Please add the following to Help | Diagnostic Tools | Debug Log Settings:
and reproduce the behavior, then send me all
idea*.log*
files from the timeframe of the reproduction. It's likely there will be several as that specific debug logging is verbose. You can attach it here or email it if you'd prefer.To set expectations properly, though, it's very possible there won't be an easy solution. IC2 already lists org metadata across up to 25 threads in parallel. It may just be that the org -- and overall instance -- are running slow this week as Salesforce finalizes the Winter '25 release. I've seen that myself, and I've heard about it from others as well. Nonetheless, let's get a debug log and see if there's anything obvious other than slow API response times.