Hi,
I get 500 errors, when using the filter "createdTime" and specifying a longer time period for the payments route. The request works when turning off the filter completely or when specifying a short time period (a year or so works)
Request:
Access token is in separate moderator's post
the error has disappeared - still Clover's API should not return 500s - probably overwhelmed or whatever...
This can happen for queries that are not constrained enough. Merchants can have a lot of orders, so querying for large time periods is problematic. Please limit your queries to avoid these issues.
Well...then it's still not good, because there should be a useful response. In addition, it worked WITHOUT filter, but it did not work WITH filter. Since the response is anyway limited to 1000 datasets, IMHO there should not be 500 errors.
I agree, but it is also not good to do open or broad queries. Just because the response is limited does not mean the query is performant.
Hi David, I did again some testing as the 500 errors are a problem for my app in production. I made a series of requests with the created_at filter and the requests are limited to a period of 30 days, which shouldn't be a problem in terms of results. The log of the requests shows that timestamps below unix time 1500000000000 returned 500 errors. I made three rounds of the same test series. 2 times the requests below this timestamp returned 500, in the other round it returned 200. All requests above this number returned 200. So maybe it is a hint on the issue on Clover's side. Logs are posted in separate moderator's post due to token.
1 Person is following this question.
