Next.js Vercel revalidation error

Developing with Prismic
5

Hmm, so does createClient actually make an API call to fetch the master ref, and if I have cache set, e.g.

const client = prismic.createClient(sm.apiEndpoint, {
    routes,
    fetchOptions: {
        next: { tags: ['client'] }
    }
});

and later in the code I would do:

const articles = await client.getAllByType("article", {
    fetchOptions: {
        next: {
          tags: ["other_tag"],
        },
    }
}

And then lets say I reinvalidate the tag other_tag, would that then cause an issue where the master ref is stale?