You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed huge amount of API requests lately in the Usage stats. After some discussion with a community engineer at Sanity.io we found that it might be caused by /listen requests in the Studio (I guess editors just leave tabs open or something).
I dug it a bit more and found that in v1 useListenQuery is used.
Could/should such requests be counted at all? (I expected no requests from Studio will be counted, but it seems requests from plugins are counted).
Does the plugin really need to use listen? Any suggestions how we can reduce count of requests? (We cannot migrate to v2 at the moment).
The text was updated successfully, but these errors were encountered:
@sorokin-energi as far as I know requests coming from the studio aren't being counted - I don't know about plugins though. I would have to check with @SimeonGriggs
@LiamMartens this ticket is kinda result of the investigation of the Community Engineer at Sanity.io. We were checking why our team exceeds API quotas considering quite a moderate amount of requests from the end customers and the most traffic was from this /listen endpoint.
Hi,
We noticed huge amount of API requests lately in the Usage stats. After some discussion with a community engineer at Sanity.io we found that it might be caused by
/listen
requests in the Studio (I guess editors just leave tabs open or something).I dug it a bit more and found that in v1 useListenQuery is used.
Could/should such requests be counted at all? (I expected no requests from Studio will be counted, but it seems requests from plugins are counted).
Does the plugin really need to use listen? Any suggestions how we can reduce count of requests? (We cannot migrate to v2 at the moment).
The text was updated successfully, but these errors were encountered: