A deleted row your cache still refuses to release

Someone deletes a todo. The database agrees it's gone. The list on screen does not.

Intermediate to advancedRead 5 minDoing: about an afternoon7 steps

What you'll have at the end

A Server Action that calls revalidatePath or revalidateTag right after the mutation, and a refreshed list on the very next load

Before you start

You need

A working Server Action that deletes one row from the database, wired to a delete control on a list already rendering from a cached read.

Not covered

A delete triggered by a webhook instead of a person's own action in the browser; that path can leave the browser's own navigation cache stale even once the server side is fixed, and needs a different fix.

Leans on

7 steps

Where to go next

A Server Action form that never shows whether it worked

use this when the person who deleted the row also needs to see it happened; this recipe only covers the list itself catching up to what the database already knows.

Checked 25 Aug 2026

Part of the NextJS cookbook