Editor: Selecting a linked document, request fails

Prismic for Content Creators
1

Hey there,
when working in the editor and trying to select a prismic document to set a link, it looks like that the request is failing. I was wondering if something changed in the editor over night, and started with a fresh browser and a new login. Nothing changed. Even across projects it doesn't work,
The browser console also returns a RequestError with the following response:

```RequestError: {
  "url": "https://document-search.prismic.io/?repository=....&localeId=de-de",
  "type": "unknown",
  "cause": {
    "name": "TypeError",
    "message": "NetworkError when attempting to fetch resource.",
    "stack": ""
  },
  "online": true
}

prismic-editor-failing-request-for-linked-docs
prismic-editor-failing-request-for-linked-docs681×749 29.6 KB

Any ideas how to fix this issue?

2

Looks like the request works again.
Thanks!

3

Hi @stefan2,

Thanks for reaching out about this! We indeed had an momentary issue with this today, it should now be fixed. Don't hesitate to let us know if you see it happening again :slight_smile:

4

hey there,

I am currently experiencing the exact same issue. Any fix or change I should be aware of?

Screenshot 2024-12-03 at 3.36.42 PM
Screenshot 2024-12-03 at 3.36.42 PM1292×1442 45.3 KB

RequestError: {
  "url": "https://document-search.prismic.io/?repository=mydoh&localeId=en-ca&customTypesIds=feature_announcement",
  "type": "unknown",
  "cause": {
    "name": "TypeError",
    "message": "Failed to fetch",
    "stack": "TypeError: Failed to fetch\n    at https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:581:386\n    at xt (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:110925)\n    at gin (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:173491)\n    at Cin (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:175775)\n    at queryFn (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:176543)\n    at Object.o [as fn] (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:75681)\n    at b (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:71275)\n    at Object.start (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:71736)\n    at gge.fetch (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:77135)\n    at _ge.fetchOptimistic (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:94473)\n    at Gnn (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:103967)\n    at Fre (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:104584)\n    at Z2 (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:571:104926)\n    at Vsn (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:573:89475)\n    at Ysn (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:573:93907)\n    at fK (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:44:19598)\n    at R3e (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:46:44250)\n    at I3e (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:46:39950)\n    at JJe (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:46:39873)\n    at rI (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:46:39723)\n    at yse (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:46:36822)\n    at o2 (https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:44:3302)\n    at https://mydoh.prismic.io/builder/assets/index-g1x3FoWs.js:46:34389"
  },
  "online": true,
  "connectionTy
5

We are running into the same issue:

Screenshot_2024-12-04_14-40-43
Screenshot_2024-12-04_14-40-431834×1692 127 KB

RequestError: {
  "url": "https://document-search.prismic.io/?repository=arcadia-website&localeId=en-us&customTypesIds=job_category",
  "type": "validation",
  "status": 200,
  "cause": {
    "issues": [
      {
        "code": "invalid_type",
        "expected": "string",
        "received": "undefined",
        "path": [
          "results",
          4,
          "title"
        ],
        "message": "Required"
      }
    ],
    "name": "ZodError"
  }
}
6

Hi @garrett.levine and @arcadia,

Sorry to hear this is still happening.

It might be a slightly different issue - can you confirm for me that if you type the title of the page you're looking for and click "try again", it then appears? If so, this is of course not the intended behavior and something we're working on fixing, but it's a workaround for now. We believe it is linked to having a document saved with no title somewhere in the repository, which is breaking the initial search results. If you're able to locate it and delete it, then it should also fix it! And we're looking at fixing that bug as well :slight_smile:

If that didn't work, please get back to me and I'll investigate further!

7

Yes, that is exactly what happens. I am unable to find any documents in the linked category that are missing titles.

8

Thank you for getting back to me. That is a known bug at the moment, we are looking into a fix, but I'm glad this workaround does the trick for the time being!

Can you send me your repository's name so I can double check that missing title theory on our end? Feel free to send me a dm if needed. Thank you!

9

It looks like we are still unable to find the page when typing in hte exact title. I'll DM you with our repository name so you can confirm the blank title issue.

12

Hi all,

Thank you for your patience as we worked through this bug, it should be all resolved now. This was linked to a storage issue on certain repositories, and shouldn't be happening again. But if you see anything out of the ordinary related to the search, feel free to reach out!

:slight_smile:

13

Confirming that this issue has been resolved for us. Thanks.

1 Like
14

It is written as DONE on Jira, but I still have this issue on my side. Created ~15 posts there is more than 4 hours. Still not appearing.

15

Hi @internal,

Thank you for reporting this. We're aware several users are currently experiencing this issue, and are working on a fix.

I'll update this thread when I have any news :slight_smile:

16

We are currently deploying a fix which should be ready in a couple of hours. You can also monitor the status here: https://status.prismic.io/.

Thank you!

17

Hello @internal,

The issue has been resolved.

1 Like