I was surprised this morning to find some of my users were active in the future. After double checking the App I quickly realized it was because they were probably using the App in Asia. This caused the set column action to input a time-stamp that is effectively in the future vs. my time.
Any fixes for this? I suppose the workaround is to check for the time difference on sign-up and subtract that in any future time-stamp actions… but I’m not 100% sure how to capture both local and user time.