Is it OK to manually invalidate cache on queryFulfilled when doing optimistic updates?

[n-ii-ma]

In here the cache is being invalidated two times if queryFulfilled rejects resulting in two network requests:

export const authApi = api.injectEndpoints({
  endpoints: (build) => ({
    getSessions: build.query<GetSessionsResponse[], void>({
      query: () => "auth/sessions",
      transformResponse: (response: { data: GetSessionsResponse[] }) =>
        response.data,
      providesTags: ["Sessions"],
    }),
    deleteSession: build.mutation<void, string>({
      query: (token) => ({
        url: `auth/sessions/${token}`,
        method: "DELETE",
      }),
      onQueryStarted: async (token, { dispatch, queryFulfilled }) => {
        dispatch(
          authApi.util.updateQueryData("getSessions", undefined, (draft) => {
            return draft.filter((session) => session.token !== token);
          })
        );

        try {
          await queryFulfilled;
        } catch {
          // Invalidate cache tag on failure to re-fetch truly up-to-date data
          dispatch(authApi.util.invalidateTags(["Sessions"]));
        }
      },
      invalidatesTags: ["Sessions"],
    }),
  }),
});

Would it be ok to add dispatch(authApi.util.invalidateTags(["Sessions"])); on the success result as well and remove invalidatesTags altogether?

       ...
        try {
          await queryFulfilled;
          dispatch(authApi.util.invalidateTags(["Sessions"]));
        } catch {
          // Invalidate cache tag on failure to re-fetch truly up-to-date data
          dispatch(authApi.util.invalidateTags(["Sessions"]));
        }
        },
        ...

[GowthamKrishna362]

        try {
          await queryFulfilled;
          dispatch(authApi.util.invalidateTags(["Sessions"]));
        } catch {
          // Invalidate cache tag on failure to re-fetch truly up-to-date data
          dispatch(authApi.util.invalidateTags(["Sessions"]));
        }

why would you have this block at all? Just use invalidateTags: ["Sessions"], and remove the block, like below?

  deleteSession: build.mutation<void, string>({
      query: (token) => ({
        url: `auth/sessions/${token}`,
        method: "DELETE",
      }),
      onQueryStarted: async (token, { dispatch, queryFulfilled }) => {
        dispatch(
          authApi.util.updateQueryData("getSessions", undefined, (draft) => {
            return draft.filter((session) => session.token !== token);
          })
        );
      },
      invalidatesTags: ["Sessions"],

As you mentioned manually invalidating it, and letting it invalide using invalidatesTags on top of that might cause redundancies. If you want to invalidate only on error or success you can use the functional form of invalidatesTags

invalidateTags: (__, error) => error? [] : tags