When modifying a user via the api I wanted to use users.updated_at as criteria for the last update. Now I noticed that it is not set anew upon all actions. Eg, when changing watched categories or watch 1st post categories, it is not. Why not? I do add new users put users to groups delete users from groups set the main group for a user alter notification levels set/unset a specific category for/from watching or watching 1st post change the email address of a user suspend/unsuspend users and believed each of these actions should alter users.updated_at. Is there another field that I’ve missed which can tell me when the settings of a user are last altered?

Watched categories are in their own table, so you’d need to check there, I think.

That would be category_users and there is no updated_at. Or is the category itself altered when a user sets it on watched?

It looks like you’re right and that there is no updated_at for the category_users table. I’m not sure how to solve your problem, you could create a user_custom_field that you updated via the API, I think.

Users.updated_at not renewed on all updates

Development

DDo (Dorothea Dorsch) May 7, 2020, 3:55pm 5

Thank you Jay, that seems to be a workaround.

Topic		Replies	Views
Change user registration date (created_at) via API Development rest-api	7	1506	July 28, 2021
How to update Watched First Post Categories for all users? Product Support	3	978	August 8, 2019
User group 'muted categories' not updating members category notifications Product Support	1	317	January 1, 2024
User profile watch/track/mute options not persisted Bug	11	1380	September 29, 2017
Creating a topic or a post sends the user_updated webhook Bug	10	2196	October 23, 2017

Users.updated_at not renewed on all updates

Related topics