You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are more session properties than there are sessions in my data.
For 476 records of sessions, I have 540 of the same property, which as far as I am aware, shouldn't be possible, as I'd imagine that you cannot have 2 of the same property on a session.
I use Umami for a native application, so the logging of data is done through the API manually. In my case, every session should have one of this property, seeing as it logs the availability of bluetooth at the startup of my app, which also means that if a session already has said data, I will send it regardless, in case it had changed.
Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
v2.15.0
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Docker
The text was updated successfully, but these errors were encountered:
Describe the Bug
There are more session properties than there are sessions in my data.
For 476 records of sessions, I have 540 of the same property, which as far as I am aware, shouldn't be possible, as I'd imagine that you cannot have 2 of the same property on a session.
I use Umami for a native application, so the logging of data is done through the API manually. In my case, every session should have one of this property, seeing as it logs the availability of bluetooth at the startup of my app, which also means that if a session already has said data, I will send it regardless, in case it had changed.
Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
v2.15.0
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Docker
The text was updated successfully, but these errors were encountered: