Something seems off with the API as of recently as our systems experienced a surge in user-engagement. The error is a 500 error, so I assume this is something the Copper Team may need to look into: :{"success":false,"status":500,"message":"could not obtain a connection from the pool within 5.000 seconds (waited 5.003 seconds); all pooled connections were in use"}
We are not receiving any 425 errors, so we aren’t superseding the request cap.
Anyone have a solution for this? This issue is causing a detrimental user-experience for our supporters.
Thanks!
Best answer by Michelle from Copper
View original