Hope SWR questions are OK here!

I'm using SWR in a situation where a user may rapidly update something, and I don't want to block them from making changes during mutation. Right now, I'm calling a server action to preform the mutation. It works fine in isolation, but if I trigger it rapidly (e.g. keep pressing a button quickly), the optimistic updates get stuck at the first one until all updates have gone through. How can I always keep the optimistic data fully up-to-date? Thanks!

useSWRMutation

  const { trigger, isMutating } = useSWRMutation(
    weeklyEventsKey,
    (_, { arg: { name, id } }: { arg: { name: string; id: string } }) =>
      updateEventName(name, id)
  );

(extremely rough prototype) trigger call:

          trigger(
            {
              name: "Event - " + new Date().toISOString(),
              id: events[0].id,
            },
            {
              optimisticData(currentData: any) {
                currentData[0].name = "Event - " + new Date().toISOString();
                return currentData;
              },
            },
          )

Action:

"use server";

import { db } from "@/db/drizzle";
import { eventsTbl } from "@/db/schema";
import { auth } from "@/lib/auth";
import { eq } from "drizzle-orm";

export default async function updateEventName(name: string, event_id: string) {
  if (process.env.NODE_ENV != "development") return;
  const session = await auth();
  // console.log(session);
  // if not auth kick out etc etc.

  // 1500ms delay
  await new Promise((resolve) => setTimeout(resolve, 1500));
  await db.update(eventsTbl).set({ name }).where(eq(eventsTbl.id, event_id));

  return true;
}