![](https://assets11.geni.com/images/external/x_com_black_16.png?1718400071)
![](https://assets13.geni.com/images/facebook_white_small_short.gif?1718400071)
By the way this problem was solved at this point in in the discussion. We got Donna's connection all working.
http://www.geni.com/discussions/139432?msg=967573
I did not want to show her path to Richard in the public discussion because of possible Private profiles at her immediate connections.
I thought Donna would have posted back saying it was ok.
When Lloyd refreshes on his computer it gives a "fresh"
Snap shot of what Geni is serving up.
The recalc icon refreshes the path on the Geni server.
You might see this in action if you have different devices, I have. One workstation will show one relationship path to a profile, another will show another.
All devices & browsers cache for performance efficiency.
Which is why the member needs to walk their tree their own self, Alex. I don't think there's a way to pass that task off elsewhere. The HistoryLink tool is the best I know of for spotting outstanding merges & tree conflicts. Once that is done and those issues resolved by a member, usually patience for server updates will do the recalc "for" you. And of course if you can see the recalc icon - press it. :):)
I feel like i repeat myself a lot.
There were no conflicts or outstanding merges in my tree.
Patience did not pay off, i have been complaining of these bad paths for months if not years, how often do server updates occur? I though there were 1/2 hourly cycles.
There were no re-calc buttons to push.
What task am i trying to pass off? The task of displaying accurate relationship paths? Surely that is Geni's task.
The relationship calculation appears to take shortcuts when possible.
If in calculating the path from you to your 8th GGF it finds that the path from you to your 7rd GGF is already cached it may start with that information and finish the path.
Where does this go wrong? Well if at some point in the past the path to your 7rd GGF was calculated oddly due to conflicts/merges that could have been cached.
What I did was find the last family member in the line to have a correct path, then go up one more. On that new profile I had the option of "refresh" on the path display. Once that newly calculated relationship was cached I walked farther up the tree one step at a time. Basically guiding the relationship calculation as to the correct path.
Caching is good because it makes the web pages load faster, but there are corner cases that make it hard to properly flush the outdated information.