Refresh event problem, when using anything other than on-load

Question

I am attempting to create a series of sequential xml loads, without any user interaction.
I.E. xml1 contains the location of xml2, and xml2 contains the location of xml3, so the next must wait until the prior xml has been loaded.
It is impractical to use dropdown lists or refresh buttons to update these - (they should all happen behind the scenes as they are just loading selections that change depending on the user privileges).
While my desired refresh-event is the when-value-becomes, I have tested when-value-changes, and found the same problem.
When I set these to automatically chain through (xml1 is set to refresh-on-load, xml2 is set to load by a trigger cell that equals "load" if there are values loaded from xml1, and so on) - the conditional refresh events do not fire.
When I use a manual refresh button, they load without a problem, and when I use a dropdown list to test the on-change or value-equals logic, this loads correctly too. So the problem is specifically during the intial load-up point, and is reproducable in any new xcelsius project I create.
To state the problem precisely, during the initial loading phase of xcelsius, the logic behind when-value-changes and when-value-equals load events does not seem to execute - however after the initial load, they fire correctly based off user input.
Is there any workaround or solution? If any clarification is needed, let me know where.

Answer 1

May not be your exact issue, but something similar -
Only a problem w/SP3 - I used dynamic visibility to hide two connection refresh buttons that were loading data after components finished. They stopped working until I turned the dynamic visibility off and just hid them behind other layers. Confirmed by revealing them after load and the triggers ran appropriately. May not be the issue (since you didn't mention visibility), but worth a try.