User "Last Seen Date" Not Updating

Bug Reports
1

I have a “user account” section in the admin area of my app to add/delete/manage user permissions and such.

When looking at my table of existing app users, the “Last Seen Date” column is almost always wrong. It shows outdated info, often times displaying no info, telling me the user has never logged in.

If I go over to the Softr user settings area for a minute (let it do it’s auto sync with the DB) and go back to my app, the info updates and shows the up-to-date latest info.

This feels like a bug to me, it doesn’t seem to be syncing with the users table when it detects a user change, only when I manually visit the Softr user area. Can this be updated so we’re not displaying old data?

2

YES, I second the lack of syncing between softr sessions and the last seen date.

My last ‘seen date’ for the app I am currently working on is from September 26, and I log in every day.

3

I went to visit my softr user’s tabs, and in 2 minutes the syncing started again. However, I was serving old data from about 4 to 6 days.

4

Hi folks!

I tested the “Last Seen” date on my end, and the data is updated in Airtable each time the User table is synced. The screenshot below shows the settings of the Date field I have in my base, which is mapped to the “Last Seen” field.

I’d also like to clarify when the two-way sync occurs, as it is not in real-time.

The sync happens when users navigate to the “Users” section of the Softr studio. In addition to navigating to the “Users” section of the app, the sync is also triggered when a user logs into the app or when you publish new app changes.

Screenshot 2023-10-03 at 17.31.43
Screenshot 2023-10-03 at 17.31.43850×1138 63.4 KB

5

Hey, thank you for the extra details about syncing.

Then I would like your advise:
Can I trust that softr will automatically update the ‘last seen’ field when a user browses my apps as a registered user, without the need for the user to enter credentials every time (relying on the active session).

The need for the app admin to Trigger manually an update for the user ‘last seen’ info, is going to make me discard ‘last seen data’ in some apps.

Here is a short experience making the efforts to bring fresh data on to that field:

1 Like
6

This is the part that is not happening today. User login does not trigger an update on that field.

7

Any word on this working as intended, instead of randomly? It still does not appear when new users log in, let alone access an app via magic link, or update when existing users log in and out, regardless if you are on the ‘Business’ plan.

:bulb: The Last Seen Date data is available to Business Plan users only.- From Softr Documentation

8

Hey @Ben @acjnas

Did you guys hear if the user activity is working? We have no idea of user activity in our app and would love to know a solution to monitor.

Thanks

9

Great question George. I know nocodeking and others gave up on it . Maybe Jonathan is still using it?

1 Like
10

Hello folks, I haven’t use this feature for a long while.

1 Like
11

I only have 1 app left on Softr and I haven’t used that feature in a while, sorry!

1 Like
12

@Jjenglert. This thread is an example of what I was referring to in our PMs.

13

Hi Team,

We use this field internally for our apps, and it’s working as intended. Nor have we heard any other cases outside of this thread that suggests it’s not working.

Are there specific apps or situations not working for you that you can direct us towards to troubleshoot?

14

@jjenglert, @artur, I can confirm that this is still the case. Logins do not trigger an update in an Airtable’s ‘Last Seen Date’ field.

Whether this works or not can be confusing, because it does update when a builder then goes to Softr’s “Users” section.

1 Like
15

Thanks for the context here.

Can you clarify if you’re talking about the last seen date in Softr or in your Airtable base?

Screenshot 2025-07-22 at 12.52.11 PM

16

Airtable Base

17

Hmm, I’m not sure that’s the intended behavior as we have this user “last seen time” in Softr. Let me check in with the team to see where they stand on this.