Next.js server action missing await

A production symptom appears first: flaky tests, stale state, slow UI, late cleanup, or growing memory. This causes stale pages, early success toasts, lost errors, and confusing production logs in Next.js apps.

Forgetting that server actions still need await for real dependencies.

Fix the root scheduling, cleanup, or concurrency pattern instead of adding arbitrary waits.

try {
  await operation();
} finally {
  cleanup();
}

The console lane proves the visible order: revalidate profile -> return ok. The active line and queues show why source order changed.

Reproduce the symptom with a small test, apply the safer pattern, then verify the flaky, slow, or leaking behavior disappears.