Open
Description
Describe the bug
As reported here: p1694347746794979-slack-C03LA109BKM, stores with high number of disputes experience long delay before showing the dispute notice.
I think we need to investigate whether useCharge()
call here results in slow database query in server.
Also, if useCharge()
can potentially cause slowness, we need to make sure such call in other places does not cause the same problem.
To Reproduce
- Have high number of disputes.
- Purchase a product with card
4000000000000259
that will generate dispute right after. - Open the order and notice the long delay before the dispute notice shows up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment