Topics created by jason

@jason Looks like a bug to me. Either a code bug (where we should update it) or a doc bug (where we should note that the lastUpdateInstant isn't changed).

Can you please file an issue about this: https://github.com/fusionauth/fusionauth-issues/issues and we'll slot that into our work queue.

For a workaround, the only thing I can think of is to listen for the user.deactivate event: https://fusionauth.io/docs/v1/tech/events-webhooks/events/user-deactivate

You could create a custom user.data.deactivateTimestamp and set that when the webhook fires.

@jason Try going to System -> Reindex and re-indexing your users. I received the same error and this resolved it for us. Everything was working on Friday for us, so it looks like something broke over the weekend.

To add to what @joshua said, we don't record when "name, username, email, or password" has changed. The last update timestamp will be modified whenever anything about a user object changes. So if you are only interested in those changes, a webhook to an external system is the best solution.

If you are ok with using the last update timestamp, I don't think you can query that with the queryString. I think you'll need to use a full query parameter. There are examples of ranges in the user search docs Joshua links to, but here's an example I copied and munged from there (so haven't tested it, but it should give you a starting point):

{ "range": { "lastUpdateInstant": { "gte": 1618691124000, "lte": 1618691224000 } } }

You'll need to escape that JSON and provide it as the query parameter (either in the url query string or in the form post object).