Hi folks!
Starting somewhere around Christmas or New Years, my frontend's requests to Xano started getting lots of failures with a CORS error message. Surprisingly, those calls didn't show up in the request history, so I assumed it was an issue with the frontend. However, after a week of scrambling to fix it ('cause this software is for a client), I'm thinking I'm maybe getting rate limited by Xano. The calls that fail tend to be the 3rd or 4th call in a sequence.
I know rate limiting shouldn't apply to paid plans like ours, but we're on a legacy plan, so I wonder if it got automatically applied somehow. I've reached out to Xano's support team directly, but I thought it might be potentially helpful data point to know whether anyone else encounters this.
I've attached images of the error messages the frontend is receiving (per my Inspect dev tools). (I blocked out the endpoint urls for security purposes.)
I was able to replicate the bug by clicking the same button a bunch of times in a row (another reason to believe it's rate limiting). This screenshot shows how the same endpoints succeed sometimes and fail sometimes.
Has anyone else encountered this?