How can I achive instant updateTag

[Sergionx]

Summary

Previously I had this 2 functions:

export async function getEnterpriseOffices(query: Query_EnterpriseOffices = {}) {
  const queryParam = new URLSearchParams();
  if (query.departmentId) queryParam.append('departmentId', String(query.departmentId));

  const response = await fetch(`office/enterprise?${queryParam.toString()}`, {
    method: 'GET',
    next: {
      tags: ['office'],
    },
  });

  if (isActionError(response)) return response;

  const result = (await response.json()) as Response<OfficeGETALL[]>;
  return result.data;
}

export async function editOffice(id: number, data: Partial<CreateOffice>) {
  const response = await fetch(`office/${id}`, {
    method: 'PATCH',
    body: JSON.stringify(data),
    next: {
      tags: ['office', String(id)],
    },
  });

  if (isActionError(response)) return response;

  if (response.ok) revalidateTag('office');

  const result = (await response.json()) as Response<Office>;
  return result;
}

And after calling editOffice the page that rendered the enterprise offices would re-render.

But now, after nextjs 16 I sustituted if (response.ok) revalidateTag('office'); with if (response.ok) updateTag('office');

If I understood correctly, now updateTag invalidates the cache from getEnterpriseOffices, but now the page does not re-render. I have to refresh the page manually or to navigate to another page and then go to the original

How can I trigger this re-render when visualizing invalidated data?

Additional information

No response

Example

No response

[Sergionx]

Also I did try to use cacheTag but since my custom method of fetch uses cokies for authentication (I just used fetch on the example for simplicity) I cannot cache it

[icyJoseph]

Do you think you can setup a small repro for this? updateTag is specifically meant to do read-your-own-writes ~ something is incorrect here.

Screen.Recording.2025-10-29.at.09.23.16.mov

Does this happen after you navigated to the edit page? Like if you refresh in edit page, and do the mutation, does that also work?

[Sergionx]

Well, my use case is more complex since I am fetching on the server, but then I use react-hook-form to update the entity and the submit function is the server action that updates the entity. I can make a video showing the important part of the code and the page. Would that work?

[icyJoseph]

Just some pseudo-code is fine, but sure a video works too, make sure to not include sensitive information.

Strange though, the server action is received by the client side router and IIRC, a header tells the router that an invalidation happened, and it acts upon that. Are you reading this data as props into a client component, and then storing it to React state or something like that? Maybe you need to re-sync the state?

[programming-with-ia]

updateTag should be called inside next(), or in the API route (the API route calls the server action).

[dennisjnnh]

why does updatetag need to throw if it's not being run in a server action? this behaviour causes so much headaches for me in the mgiration to next 16, as i was heavily using revalidateTag and needed to migrate to the updateTag call