You can log back in here.
As kbbob mentioned, it was likely the cache needing time to catch up.
Can you see it updated now? :)
Glad to hear! Locking this up as resolved. :)