What do you define as ‘enough information to be useful’?
For data privacy reasons you are not likely to get access to address information or birthdates.
If issues like the one above aren’t sent to the office, will the players MSA page eventually update automatically to show the correct expiration date or will it always show the wrong expiration date?
Our developers agree there’s a problem somewhere, it appears to me that not all the membership updates are being logged to the file that is used to know what records to update on MSA.
If there’s a subsequent update to one of these IDs that does get logged, then that record would get updated on MSA. That’s why some of these problems go away but others don’t.
We’re working on generating a list of IDs that need updating as a one-time fix, I don’t know how they’re doing on solving the underling problem of logging failures.
It appears quite a few of the memberships that were coming up as either missing or without a current membership expiration date have been updated, there may still be additional updates in progress.
I think this is the result of a list of 301 IDs with issues in them that I sent the developers on Friday, not from finding and fixing the underlying cause.
But it appears to be an improvement for TDs and players.
I think a similar thing happened to me. In my case I did a new membership and a renewal in the same batch, and both of them have not been updated on MSA.
It seems like this delay is longer than usual.
It’s hard to address issues without details.
As noted on the home page, there was a maintenance window today, to do an upgrade on the database server that supports MSA. Updates of the MSA member data were suspended ahead of this upgrade and will hopefully be resumed yet this afternoon.
Everyone is concerned about their rating performance… 
This topic was automatically closed 730 days after the last reply. New replies are no longer allowed.