Various connection problems after sandbox was refreshed

[Christopher Sorrows]

Our full copy sandbox just got refreshed, I updated my security token for the connection, and it tests fine, and I was able to refresh the metadata, but some operations hang or don't work right.

For example, if I do a "Compare With", it just hangs in a pending state.  It never actually completes retrieving the code and doing the comparison.

If I do a "Deploy Modified Metadata" on some updated code I know is a later version (modified) than what is it the sandbox, it does some comparison of the server state, and comes back with "Deployment Complete / All files are up-to-date" even though I know for a fact what I'm trying to deploy is different.

It almost looks like some information about the state of the old sandbox has been cached, and now that the sandbox has been refreshed, it's out of sync and causing problems.

Any ideas on fixing this?  BTW I'm running IDEA 2023.2.4 (Ultimate Edition) and Illuminated Cloud 2.2.8.8 (I know these are older versions, but I tend not to update my environment unless I encounter bugs or need a new feature).

Thanks!

[Scott Wells]

Hi. Let’s break this down a bit into the constituent issues you’re seeing.

First, if you see things hanging in a pending state, that’s the Salesforce Metadata API’s retrieve API saying that the retrieve request has been received and it sitting in queue waiting its turn. There’s nothing that IC can really do about that. Often job queue issues are transient, but if you continue to see that, you should log a support case with Salesforce. You can provide the specific job IDs — which are available in idea.log — to help support find these “stuck” jobs and figure out why they’re sitting in queue so long.

Regarding Deploy Modified Metadata potentially not reconciling local vs. server state, you can enable debug logging for Metadata Deployment, reproduce the behavior, and see in idea.log the exact comparisons being performed. For a better signal-to-noise ratio, you might start with one or two metadata files that you know to be out-of-date so that you can easily see the timestamp comparisons that IC is using to determine what it things is out-of-date.

I’m very happy to look at log extracts for both/either of these if you’d like. Feel free to email the logs to me for review, ideally providing some context of expected vs. actual behavior to help guide my analysis of the log contents.

Regards,
Scott Wells

​

[Christopher Sorrows]

Hi Scott - Thanks for the reply!  Regarding the first issue, when I do a "tail -f idea.log" I don't see anything getting logged when I issue the compare operation, I only see info logged after the compare finishes, when used to only take a few seconds but now takes a minutes or more.  Is it expected that logging is done only at the completion of the compare?  I'll send you a log snippet from that in a separate email.  The compare itself seems to be functioning as expected, it's just taking much longer than it used to.

Regarding the second issue, I'll try enabling that logging tomorrow and see what's in there.

Thanks!

- Chris