API down for days on one repo, cloudfront or CORS issue?

Developing with Prismic
1

API access to one of 2 of my repos has been down for at least a week.

No code changes. Graphql gatsby builds work, but not API v2 client requests.

Here's an example failing url that the client is hitting:
https://bassu.cdn.prismic.io/api/v2/documents/search?integrationFieldsRef=bassu~1cbb0425-ac82-41b3-a07f-2491d35c1051&page=1&pageSize=100&ref=YFukVBMAACEApqHT&q=[[at(document.type%2C%20"article")]]

Chrome is alerting no CORS header
No 'Access-Control-Allow-Origin' header is present on the requested resource.

and in the failed response
x-cache: Error from cloudfront

3

Hello @matt2

Welocme to the Prismic Forum.

I can see the API is working fine now in chrome browser. Can you try again?

Priyanka

4

I see that it started working again. Did someone do something?

However, now the other repo is failing in the same way

https://omniafishingcom.cdn.prismic.io/api/v2/documents/search?integrationFieldsRef=omniafishingcom~b869e865-a526-4c5d-b559-d7af52a467da&page=1&pageSize=100&ref=YGzPkhAAACAA68LB&q=[[at(document.type%2C%20"video")]]

What is going on?

5

Hello Matt,

Nothing has changed from our side, but I see It's working well with the other repo. I can see the API.

I am not sure what is happening so I am going to share this with my team.

Thanks

Priyanka

8

This continues to be a big problem. Now site builds are broken.

The above links are failing, and this is the one that failed on the build:

https://bassu.cdn.prismic.io/api/v2/documents/search?integrationFieldsRef=bassu~9eba041d-5d8d-46ed-aad5-0b2d699a7037%20%20&page=1&pageSize=100&fetchLinks=&lang=en-us&ref=YFukVBMAACEApqHT&q=[]

10

Hello @matt2

I am sorry that you are facing trouble. I've updated my dedicated team about this issue. I'll let you know once I hear back from them.

Thanks,

Priyanka

12

Hello @matt2

It gets fixed now. Let us know if you still experience issues with the API.

Thanks

Priyanka

13

OK, I will keep an eye on it. Thanks.

And to clarify, was something wrong and some action was taken?

14

Hello @matt2

Yes, the issue is from our side when we migrate this repository to another cluster. We have added a note to not move this repo to another cluster.

Let me know if you still get the same issue.

Thanks,

Priyanka