Open paulreimer opened 5 years ago
Cannot reproduce. Investigated the code path, there isn't anything being cached to prevent this scenario.
One thing to note, there is a 2 min delay (hard-coded, but could be changed to any number) on re-assigning member tags (if they are fresh tags, there is no delay). This delay applies to the recent "Tag ID" dropdown/select (the number could be entered manually in the text entry), and prevents the same tag from being assigned multiple times.
The following steps produce an unexpected issue where the website does not seem to register Front Desk sign-ins, when the following events have occurred:
Expected: The new user details should show up as the latest "Front Desk" sign-in Actual: The website does not update to show the new user details -- no change/old user details still shown.
Scanning any other tag, or searching for any other user, and then scanning the re-assigned tag, will produce the expected behaviour.