question

almosteric avatar image
almosteric asked Jeffrey Blattman commented

API Getting a lot of Gateway Timeout errors

Starting around 12:45 UTC, we started seeing serious performance degradation of the API - most (but not all) of our calls are either getting 504 Gateway Timeout errors, or just taking a really, really long time to execute

REST API
10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ankitmalviya avatar image
ankitmalviya answered

Hello,


Are you still experiencing this? It should be working fine now.

Can we have screenshot or video of API where it is throwing error.


Thanks,

Ankit

10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

almosteric avatar image
almosteric answered

We don't seem to be getting errors anymore, but the API is definitely being much slower than normal

10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ankitmalviya avatar image
ankitmalviya answered

Due to high traffic server can have load and due to it response time can be slow. We are aware of it and working consistently to improving our API performance.

Apologise for the inconvenience.


10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

almosteric avatar image
almosteric answered Jeffrey Blattman edited

Are there any plans of changing how the API throttling works? While I understand why API rate limiting is necessary, but currently it is based on our Application ID, which means as we get more customers they have to share a fixed amount of bandwidth - this is the exact opposite of how an API should scale.

Most other APIs base their limiting on the individual location.

1 comment
10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

If this was rate limiting you'd receive a 429, not 504. See: https://docs.clover.com/docs/api-usage-rate-limits. Rate limiting is also based on token, which is essentially "per-site" correct? You're right there is still an upper bound for the app.

You can petition developer relations to have your rates raised. You'd want to make sure you've first considered the best practices here: https://docs.clover.com/docs/api-usage-rate-limits#best-practices-to-avoid-429-http-error-messages first.

0 Likes 0 ·
shopventory avatar image
shopventory answered Jeffrey Blattman commented

Hi there,

We are also seeing some slower than usual api performance. Are there any baseline numbers on how fast an item create/update should take? Is there any data we can gather that would help the Clover team determine if there are bottlenecks?

Much appreciated,

-Rares @ Shopventory

1 comment
10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

The endpoints, what's baseline, and what you're seeing would help.
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community