🐛 Possible Bug - Possible race condition on CA server
-
Environment Observed
- Where was the issue observed? CA
- Account Name alumniUBC
- Account ID account-109-A
-
Is this a converted account?
- No
- Date Converted (if known)
-
Issue Scope
- How widespread is the issue? All customers
- Event Name testign Jun 5, 2026 (note: it is a test event)
- Event ID event-105177-A
-
Was the issue reported by the client?
- Yes
- Client Contact Name (if yes) Gordon Purchase
- Client Contact Email (if yes) gordon.purchase@alumni.svc.ubc.ca
-
What’s the problem?
- When you edit an instruction set, type really fast, hit Tab to get to the Save button and hit enter sometimes the content will not save.
-
Is the issue reproducible?
- Yes
-
If reproducible, where?
- Pitstop
- Pitstop Account @the Grounds - account-1551-A
- Pitstop Event ID Celebration of Life- Tom Peterson Jul 15, 2026 event-44397-A
-
Steps to reproduce the issue
- First turn of Grammarly if you have it enabled. I found that it provides enough of a buffer that the issue does not appear, and Gordon does not have that installed.
- Go to the Celebration of Life event
- Choose one of the General Instructions on the Event-Wide function
- Edit the instruction
- Type really (can be any garbage) and then Tab to the Save button and hit Enter.
- Repeat several times
- Sometimes no content will be saved; other times some of the content will be saved.
-
Expected behavior
- Not sure if this is an actual bug or not. If you slow down or even take the time to mouse over and click the Save button, it works just fine.
-
Troubleshooting steps already taken
- I did some checking, and it looks like it could be a race condition where the system is failing to keep up. No other clients have reported this so I cannot say what the criticality is.
-
Workaround identified?
- Yes
- Type slower :)
-
Attachments available?
- Screenshots or videos: video file is attached to the Zendesk ticket. I put it in a note at the end of the ticket.
- Zendesk ticket link (for Support use)
Please sign in to leave a comment.
Comments
0 comments