Suddenly can't access our date

Feature(s) impacted


Observed behavior

When we try to access any of our collections, it usually throws an error (sometime it’s successful instead and not necessarily the same error in the same situation). The error is usually a CORS error but there have also been a couple of timeout errors.

Expected behavior

When we try to access data, it is presented.

Failure Logs

Access to XMLHttpRequest at ‘[schedule]=id%2Csubscription%2CloanNumber%2Cvendor%2Camount%2CenableAutoPay%2CstartAt%2CperiodType%2CperiodCount%2CperiodLength%2CamountUSD%2Cstatus%2CcreatedAt%2CloanType%2Ccurrency&fields[subscription]=id&page[number]=1&page[size]=10&sort=-createdAt’ from origin ‘’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.


  • Project name: Scratchpay
  • Team name: Developer and Support have same issue
  • Environment name: Production
  • Agent type & version: ??
  • Recent changes made on your end if any: One change to add collection item to Support layout.

Hey @Brett_Belka :wave:

Any way you can share with us a small video clip of the issue?
Alors, do you have any other particular logs, either in your browser or in your agent that can help investigate your issue?

Thanks in advance

Hi Jeff!

Thanks for getting back to me. It seems to work fine today but it was literally every collection that in our project couldn’t retrieve any data and the console showed a CORS error (the same as in the post, though obviously the address depended on the page…).

Thanks again for the response.

Nevermind. It’s back. Attached are two screenshots. This page loaded ~10 minutes ago. Now I get this.


If that’s possible for you, could you try the following:

  • Go to your “Network” tabs of your developer console
  • Whenever a call to your server fails, right click on it and copy it as “curl”
  • Run it in a terminal and send me the response, either here with obsfucated credentials or via DM?

Thanks in advance :pray: