I could not reproduce this situation by performing the following steps:
- Ensure a database connection user with email
- Going to the previously mentioned user profile in the Dashboard and selecting the Block User action from the menu.
- Performing a GET
The above steps lead to a response containing the
blocked: true attribute/value. I also then unblocked the same user and did another search request which showed the unblocked change. The user search is not synchronous in relation to the operation that updated the user so in a normal scenario there may be a slight delay, but in general it will be almost instantaneous.
You mention that you observe this for other attributes; can you also indicate what happens if you update the user metadata through the dashboard and then perform a search that would return that user (if you repeat the search after some time/seconds is the result the same). In addition, updating the question with the exact type of user (connection) and the exact steps on how it was created/blocked/updated
may be helpful for troubleshooting purposes.