Hello, I have my route resolver setup with the Client export const Router = { routes: [ { type: "magazin_single_post", path: "/:lang/blog/:category/:uid", resolvers: { category: "category", }, {...ETC} }, ], href: (type) => { const route = Route…

I can also confirm that past builds - I am using vercel so I can rebuild commits and branches from the past - have the same issue, which means it doesn't come from package versioning/mistake in the code.

@jake @will @DavidParys It doesn't look like a problem with the API. Could you share your project files with me so that I can try debugging? You could send me a ZIP file or invite me to a git repo (github username samlfair).

I might be onto something, Which endpoint should be used for fetching data? https://[repoName].prismic.io/api/v2 or https:/[repoName].cdn.prismic.io/api/v2 Here's where the confusion comes from.

I think you may well be on to something! We're currently using (and have been using for some time without issue) the https:/[repoName].cdn.prismic.io/api/v2 version, from a quick test if we change to https:/[repoName].prismic.io/api/v2 (without cdn) the url field is returned as expected. But as you…

Hey @DavidParys @will , You should definitely use the CDN. It improves response times and scalability. But it's really interesting that that makes a difference. I'll report that the dev team. Sam

@DavidParys Does it work for you if you remove .cdn from the endpoint?

@samlittlefair Yes! Definitely, without the .cdn, the URL field is returned and works perfectly fine

This is extremely strange. We can't think of any reason why there would be a difference between the CDN and the main API. We can't reproduce the issue on our side. Could you share your project with me, so I can try to reproduce it? Sam

It's strange indeed. Unfortunately I wouldn't be able to share the projects' files with you as this is a company owned project. Though I could isolate the pages in question in a separate project if that would work for you? Could also share the prismic repository as well

@DavidParys If you could create a separate project that recreates the issue, that would work for me. I've looked at the repository, and the Route Resolver works fine for me, but I'm testing it in a very different context from you.

Routes not returning URL anymore?

Developing with Prismic

Topic		Replies	Views
Some document URLs breaking after resolving with Prismic client routes Developing with Prismic nextjs , slice-machine , fetch-linked-content	8	92	July 31, 2025
Builds suddenly failing with 500 errors Developing with Prismic rest-api	17	806	May 23, 2022
Access to fetch at 'https://...' has been blocked by CORS policy Developing with Prismic reactjs	11	4152	October 1, 2022
Route Resolver Error: An invalid API response was returned Developing with Prismic nextjs , link-route-resolver	11	587	March 7, 2024
Prismic API returning stale data Developing with Prismic nextjs	6	118	July 24, 2024

Routes not returning URL anymore?

Related topics