-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigation of double distribution occurance #4783
Comments
I am definitely seeing multiple requests coming in at the exact same time. This seems to be because the request timed out. I'm seeing a request taking over 48 seconds and nginx returns an error 499. I'll bet that this causes the button to re-enable and the user clicks again at that point. We need to fix our slow queries. EDIT: Validated that when this happens the user actually gets an error screen. They can then click back and go back to the request page and do everything again since at that point the request hasn't been fulfilled yet. That seems to be what happened. |
I'm wondering if this has something to do with vacuuming - maybe it happens to be going on at that exact moment. |
Noting that during the planning meeting we determined that vacuuming wasn't happening at the time of the issue. |
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned. |
Automatically unassigned after 7 days of inactivity. |
Summary
Investigation of the issue covered in the support log at Nov 12, 2024, 11:17.
Please check into the logs and see if there are any further clues there.
We had thought this was a double-click on the distribution confirmation, but there has been a fix put in to cover off that situation.
Things to consider
No response
Criteria for Completion
Investigate and report back to the Sunday planning meeting.
The text was updated successfully, but these errors were encountered: