Another small treeshare problem

Instead of making second changes on Ancestry I wonder if using “Reset TreeShare” would force those changes to appear? It will make collecting changes take long as it rebuilds the new .DT11 file.

I’m pretty sure that it will. I tried that a few days ago at your suggestion and it did then. The only problem is that treeshare took 3 1/2 hours to run; I can’t do that every day. One thing to look out for, and I don’t remember the answer to this, is whether the changes made appeared as having changed after running reset treeshare. I suspect that they won’t, so that it will be like looking for a needle in a haystack to find them, if I have not first made a list, and if I have made a list it is quicker to go back in and change them again.

Despite the time that it takes, I will run reset treeshare again sometime soon and pay close attention to what happens.

1 Like

16.29 Taipei time, 9.29am London, 8.29 am GMT 12 July. Just a quick update to say that I used Ancestry and Treeshare at various times throughout the day yesterday and rather fewer times so far today without noticing any problems.

This does not look like an issue in which there is a systematic problem at specific times of day because, for example, the dates are temporarily out of synch.

Several days later at 6.30 pm in Taipei. I was going to report that I had made various low volumes of changes over the past few days and was just coming to the end of a large series of updates today without having encountered any further problems, and then I spotted this

The blank line under Gerard Edgcombe Palmer’s first spouse should have been filled by his second, Sheila P Morton. I created this family all at one time earlier on today, and yet Gerard and one of his two wives have appeared in Treeshare and the second wife not. (She appeared when I made a subsequent change to her in Ancestry and then re-ran treeshare.)

This re-enforces my view that problems are pretty random, although clearly they sometimes last for a while, affecting everything that happens in a certain period.

Luckily, after finishing my updates, I have the same number of people in Ancestry and RM, although I may well have missed some additional records added to existing people.

Same day at 19.55 Taipei time, 12.55 London, 11.55 GMT. After writing the last post, I have created a new family with about a dozen new people, amending a few existing people along the way. When I ran treeshare, none of the changes appeared.

I went back in and edited two of them and they did appear. I will now work through all the others.

This does sound like something to be addressed by Ancestry. The difficult thing is Ancestry Support will immediately refer you back to RM as soon as you mention the API. You could ask if they will transfer it to the right development team.

1 Like

Having not posted on this topic for some time, I now have an update with an issue I have not seen before.

Over the past month or so, I have carried on using treeshare most days, usually without problems. I have been running treeshare more frequently than before, so that any problems that do occur should be isolated. Sometimes I have seen an issue. For example, a few days ago, I made some changes in Ancestry, ran treeshare immediately, noticed that the final one of my changes had not been reflected, went back into Ancestry and amended the person again, fixing the problem. All this happened within a couple of minutes; ie during that time a change to Ancestry and not caused an update and very shortly thereafter another date did.

Over the past couple of days, I have added lots of people and was concerned when I checked and found that I had thirty fewer people in RM than in Ancestry. In the past, I have fixed problems like this by going back through my browser history and identifying those who were missing, but this time I couldn’t see the source of the problem. So in the end, I ran ‘Reset treeshare.’ The next treeshare update took 90minutes as expected, and I have just started paging through the 68,000 records in the treeshare screen (none of which shows up as changed) looking for my missing people. (I figured that I could look a screen at a time for blank RM icons.)

Then in passing, I noticed this

As you will see, the screen is for Vernon Coleridge Boles. The detail shows him as present on RM but not on Ancestry, but the index on the left shows him present in both systems.

Paging down a little further, I found another example of the same thing

To repeat, this was immediately after running ‘reset treeshare’ and then running the main treeshare update. I had expected everything to be refreshed and consistent. It is a little alarming to see that even after doing this the data in the system is evidently internally inconsistent; something is clearly missing or corrupt. (These are not people whom I have updated recently.)

I haven’t yet found any of my missing people, but so far I am only down to surnames beginning with d.