Hi team,
We’re trying to understand how last_interacted_at should be used for implementing user inactivity timeouts.
From our observations, the value appears to be continuously updated with the latest interaction timestamp, for example:
“last_interacted_at”: “2026-07-27T06:55:21.428Z”
Because this field always reflects the most recent interaction, we’re unclear on how it can be used to reliably calculate an inactivity period (for example, automatically logging a user out after 30 minutes of inactivity using post-login action).|